Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New test: ensure user-facing options are being propagated to the runtime payloads #247

Open
wainersm opened this issue Aug 15, 2023 · 0 comments
Labels

Comments

@wainersm
Copy link
Member

This test is an idea of @fidencio in #239 (comment) , I am just trying to record and put more details in here.

Add a new test case in https://github.com/confidential-containers/operator/blob/main/tests/e2e/operator_tests.bats to ensure the user-facing options are being propagated to the CCRuntime payloads.

Example: the default CCRuntime deployment (https://github.com/confidential-containers/operator/blob/main/config/samples/ccruntime/default/) will pass the runtimeClassNames, defaultRuntimeClassName, and debug parameters to quay.io/confidential-containers/runtime-payload via kustomizations (https://github.com/confidential-containers/operator/blob/main/config/samples/ccruntime/default/kustomization.yaml#L16).

Those parameters are passed via CCInstallConfig (https://github.com/confidential-containers/operator/blob/main/config/crd/bases/confidentialcontainers.org_ccruntimes.yaml#L87). On the runtime-side, properties are passed as environment variables (https://github.com/kata-containers/kata-containers/blob/main/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml#L27) to the installer script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant