search

confidential-containers / documentation

Documentation for the confidential containers project
Apache License 2.0
73 stars 48 forks source link

quickstart: Update to using kustomize with the ccruntime sample payloads #89

Closed fidencio closed 1 year ago

fidencio commented 1 year ago

During the v0.3.0 development cycle we've changed to using kustomize with the ccruntime and ssh-demo sample payloads, so we need to reflect it here.

As the v0.3.0 is not yet released, one can test the changed by using 4a41c6fd66921a2a56bbf7762d92cf37ddf568ed as ref, as shown below:

kubectl apply -k github.com/confidential-containers/operator/config/samples/ccruntime/default?ref=4a41c6fd66921a2a56bbf7762d92cf37ddf568ed

Or, for s390x:

kubectl apply -k github.com/confidential-containers/operator/config/samples/ccruntime/s390x?ref=4a41c6fd66921a2a56bbf7762d92cf37ddf568ed
fidencio commented 1 year ago

/cc @BbolroC @stevenhorsman @mythi @fitzthum

fidencio commented 1 year ago

The only thing I'll note is that I initially Icreated a VSI with 2vCPU & 8GiB RAM, which matches the pre-req in our doc: Ensure a minimum of 8GB RAM and 2 vCPU for the Kubernetes cluster node, but when I deploy the operator, I hit an error

Oh, I could reproduce the same error here, and I also could reproduce the error here using v0.2.0.

stevenhorsman commented 1 year ago

Quick update - I've just realised that my normal test VM are 4CPU, 8GB RAM, not 2, so that might make the difference.

fidencio commented 1 year ago

Quick update - I've just realised that my normal test VM are 4CPU, 8GB RAM, not 2, so that might make the difference.

Everything does work as expected using 4CPUs, and I'm also updating the docs accordingly, thanks for bringing this up!