github/confidential-containers
1
0
Fork 0
mirror of https://github.com/confidential-containers/confidential-containers.git synced 2025-08-22 17:45:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

quickstart: Adapt to the operator using kustomize

Browse Source 
Let's adapt the instructions to using kustomize for deploying the sample
ccruntime custom resource.

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio 2023-01-17 09:59:11 +01:00 committed by Fabiano Fidêncio
parent 0c2ea2f441
commit 41d23524f7
1 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
quickstart.md
View File

@ -78,7 +78,19 @@ Creating a custom resource installs the required CC runtime pieces into the clus
the `RuntimeClasses` the `RuntimeClasses`
``` ```
kubectl apply -f https://raw.githubusercontent.com/confidential-containers/operator/main/config/samples/ccruntime.yaml kubectl apply -k github.com/confidential-containers/operator/config/samples/ccruntime/<CCRUNTIME_OVERLAY>?ref=<RELEASE_VERSION>
```
The current present overlays are: `default` and `s390x`
For example, to deploy the `v0.3.0` release for `x86_64`, run:
```
kubectl apply -k github.com/confidential-containers/operator/config/samples/ccruntime/default?ref=v0.3.0
```
And to deploy `v0.3.0` release for `s390x`, run:
```
kubectl apply -k github.com/confidential-containers/operator/config/samples/ccruntime/s390x?ref=v0.3.0
``` ```
Wait until each pod has the STATUS of Running. Wait until each pod has the STATUS of Running.
@ -280,11 +292,11 @@ We have prepared a sample CoCo operator custom resource that is based on the sta
Support for multiple custom resources in not available in the current release. Consequently, if a custom resource already exists, then you'll need to remove it first before deploying a new one. We can remove the standard custom resource with: Support for multiple custom resources in not available in the current release. Consequently, if a custom resource already exists, then you'll need to remove it first before deploying a new one. We can remove the standard custom resource with:
``` ```
kubectl delete -f https://raw.githubusercontent.com/confidential-containers/operator/main/config/samples/ccruntime.yaml kubectl delete -k github.com/confidential-containers/operator/config/samples/ccruntime/<CCRUNTIME_OVERLAY>?ref=<RELEASE_VERSION>
``` ```
and in it's place install the modified version with the sample container's decryption key: and in it's place install the modified version with the sample container's decryption key:
``` ```
kubectl apply -f https://raw.githubusercontent.com/confidential-containers/operator/main/config/samples/ccruntime-ssh-demo.yaml kubectl apply -k github.com/confidential-containers/operator/config/samples/ccruntime/ssh-demo?ref=<RELEASE_VERSION>
``` ```
Wait until each pod has the STATUS of Running. Wait until each pod has the STATUS of Running.
``` ```