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

Research a solution to allow operator rejects requests using not allowed Kubernetes API versions. #227

Open
Tracked by #379
jvanz opened this issue May 17, 2022 · 2 comments

Comments

@jvanz
Copy link
Member

jvanz commented May 17, 2022

Bad actors could deploy workloads using features (API versions) not cover by the admission controller. Thus, bypassing the validations. We should look for a solution of how to prevent this to happen.

Issue from threat #14 of the threat model. One solution proposed during RFC discussions is a policy that rejects all the workloads using API version different from a defined allow list

NOTE: This is an issue created from RFC discussing the admission control threat model. It's created to allow the Kubewarden team discuss the proposed mitigation further and start to work on each actionable item when possible

@viccuad
Copy link
Member

viccuad commented Sep 21, 2022

As an example, there is https://github.com/FairwindsOps/pluto as a CLI tool to discover deprecated apiVersions of resources.

@viccuad
Copy link
Member

viccuad commented Jun 23, 2023

This is partially implemented by https://github.com/kubewarden/deprecated-api-versions-policy.

It is missing a policy with an allowlist for api versions.

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

No branches or pull requests

2 participants