From d4b66b5293afad3cc86a0c08f95a3ce5f022836b Mon Sep 17 00:00:00 2001 From: Francesco Cheinasso Date: Sun, 5 Nov 2023 12:29:52 +0100 Subject: [PATCH] Updated Links --- .github/workflows/lint.yml | 3 +-- infrastructure/certificate-provisioning/README.md | 2 +- operators/README.md | 2 +- 3 files changed, 3 insertions(+), 4 deletions(-) diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml index 110404c0d..272735ec3 100644 --- a/.github/workflows/lint.yml +++ b/.github/workflows/lint.yml @@ -99,11 +99,10 @@ jobs: persist-credentials: false - name: Check the validity of the links in the documentation - uses: gaurav-nelson/github-action-markdown-link-check@v1 + uses: gaurav-nelson/github-action-markdown-link-check@1.0.15 with: use-quiet-mode: 'yes' - shell-lint: name: Lint shell files runs-on: ubuntu-latest diff --git a/infrastructure/certificate-provisioning/README.md b/infrastructure/certificate-provisioning/README.md index 61502d7f2..3ea80d131 100644 --- a/infrastructure/certificate-provisioning/README.md +++ b/infrastructure/certificate-provisioning/README.md @@ -118,7 +118,7 @@ In different scenarios, it may happen to have different `Ingress` resources in d ### Install kubed -Kubed can be easily installed with helm [[5]](https://appscode.com/products/kubed/latest/setup/install/). +Kubed can be easily installed with helm [[5]](https://appscode.com/products/kubed/v0.12.0/setup/install/). ```bash helm repo add appscode https://charts.appscode.com/stable/ diff --git a/operators/README.md b/operators/README.md index e818b8131..59164674d 100644 --- a/operators/README.md +++ b/operators/README.md @@ -108,7 +108,7 @@ The two main limitations of this approach are the following: If the request for a new snapshot is valid, a new Job is created that performs the following two main actions: -- **Export the VM's disk**: this action is done by an init container in the job; it steals the DataVolume from the VM and converts the above raw disk image in a QCOW2 image, using the [QEMU disk image utility](https://qemu.readthedocs.io/en/latest/tools/qemu-img.html). After the conversion, it creates the Dockerfile for the Docker image build, which is needed in the next step. +- **Export the VM's disk**: this action is done by an init container in the job; it steals the DataVolume from the VM and converts the above raw disk image in a QCOW2 image, using the [QEMU disk image utility](https://qemu.readthedocs.io/en/master/tools/qemu-img.html). After the conversion, it creates the Dockerfile for the Docker image build, which is needed in the next step. - **Build a new image and push it to the Docker registry**: once the init container terminates successfully, an EmptyDir volume with the building context is ready to be used for building the image and pushing it to the registry. This job leverages [Kaniko](https://github.com/GoogleContainerTools/kaniko), which allows to build a Docker image without a privileged container, since all the commands in the Dockerfile are executed in userspace. Note that Kaniko requires a large amount of RAM during the building process, so make sure that the RAM memory limit in your namespace is enough (currently the Kaniko container has a RAM memory limit of 32GB). When the snapshot creation process successfully terminates, the docker registry will contain a new VM image with the exact copy of the target persistent VM at the moment of the snapshot creation. Note that before being able to create a new VM instance with that image, you should first create a new Template with the newly uploaded image.