-
Notifications
You must be signed in to change notification settings - Fork 199
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
Kubernetes driver for command tests #311
Comments
I would also be interested in using this testing framework on Kubernetes clusters especially OpenShift where docker daemons are not present. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #270 , it would be extremely convenient to be able to use a Kubernetes native driver to run both image content tests (the currently supported test types using
--driver tar
) as well as command tests that could run as pods against an image-under-test.This is an oversimplification but at a HL, a new driver of type
kubernetes
is created which can use an existing user's KUBECONFIG context and executeskubectl run cst-pod-randomid --image=image-under-test --command -- <cmd> <args...>
for each command test indicated. Instead of inspecting the Docker/containerd socket for completion status, verify pod status, exit code, etc.There are some obvious edge cases such as running pods in a secure environment (gVisor, Openshift, clusters with PodSecurityContext, etc) that may prevent this outright. But I'd still like to entertain the idea for those in shared environments that may not have access to a Docker/containerd host directly.
The text was updated successfully, but these errors were encountered: