You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: config/peerpods/podvm/README.md
+32
Original file line number
Diff line number
Diff line change
@@ -34,3 +34,35 @@ Now when you create a KataConfig with `enablePeerPods: true` with empty
34
34
`AZURE_IMAGE_ID` or `AWS_AMI_ID` in `peer-pods-cm`, then depending on the cloud
35
35
provider configured, the operator will create the pod VM image based on the
36
36
provided config.
37
+
38
+
## PodVM Image Upload Configuration
39
+
40
+
The PodVM image can be embedded into a container image. This container image can then be unwrapped and uploaded to the libvirt volume specified in the `peer-pods-secret`. Please note that this feature is currently supported only for the libvirt provider.
41
+
42
+
To create an OCI image with the PodVM image, you can use the `Dockerfile.podvm-oci` as follows:
In this context, `PODVM_IMAGE_SRC` refers to the location of the `qcow2` image on the host. Optionally, you can also set `PODVM_IMAGE_PATH`, which is the path of the qcow2 image inside the container. This path will be used as `<image_path>` in the `PODVM_IMAGE_URI` as described below.
51
+
52
+
`oci` is the only supported `image_repo_type` at present.
53
+
54
+
Ensure that `PODVM_IMAGE_URI` is configured in the `libvirt-podvm-image-cm` in the following format:
In this example, `<image_tag>` and `<image_path>` are optional. If not provided, the default values will be `<image_tag>`: `latest` and `<image_path>`: `/image/podvm.qcow2`.
67
+
68
+
**Note:** When pulling container images from authenticated registries, make sure that the OpenShift `pull-secrets` are updated with the necessary registry credentials.
Copy file name to clipboardExpand all lines: config/peerpods/podvm/podvm-handling.md
+6
Original file line number
Diff line number
Diff line change
@@ -133,3 +133,9 @@ delete the image gallery defined in the `IMAGE_GALLERY_NAME` key in
133
133
configMap is updated with empty value (""). Also the annotations
134
134
LATEST_AMI_ID (for AWS) or LATEST_IMAGE_ID and `IMAGE_GALLERY_NAME` (for
135
135
Azure) are removed from the `peer-pods-cm` configMap
136
+
137
+
## PodVM Image Upload flow via OSC operator
138
+
139
+
* The code verifies all the required config parameters
140
+
* Based on the `PODVM_IMAGE_URI` presence on the cloud provider specific configMap (eg: `libvirt-podvm-image-cm`), `IMAGE_TYPE` is set to either `operator-built` or `pre-built`.
141
+
* Based on the `IMAGE_TYPE` it will invoke the create image from scratch for `operator-built` and pull an existing image if it's `pre-built`.
0 commit comments