We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When running the operator e2e tests on a KinD cluster, we should do the following:
PodSecurity
Ideally the operator should run in a namespace with the restricted profile enforced.
restricted
This requires the operator to run on a cluster with Kubernetes 1.22 or higher.
Originally posted by @gabemontero in #28 (comment)
The text was updated successfully, but these errors were encountered:
Note that with #56, we can bump our k8s e2e test version to 1.22 or 1.23
Sorry, something went wrong.
This is now obsolete - PodSecurity Admission graduated to stable in k8s 1.25 (on by default)
No branches or pull requests
When running the operator e2e tests on a KinD cluster, we should do the following:
PodSecurity
admission pluginIdeally the operator should run in a namespace with the
restricted
profile enforced.This requires the operator to run on a cluster with Kubernetes 1.22 or higher.
Originally posted by @gabemontero in #28 (comment)
The text was updated successfully, but these errors were encountered: