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

Checking Kubernetes clusters fails because v1/PodSecurityPolicy is checked, though it does not exist in the K8s API #245

Closed
shurkanTwo opened this issue Feb 15, 2023 · 2 comments · May be fixed by #246

Comments

@shurkanTwo
Copy link

Describe the bug

When checking a cluster that is running Kubernetes 1.24.X, popeye fails with the following error message:

Boom! No resource meta found for policy/v1/podsecuritypolicies

This should be due to the fact that PSPs have never graduated to v1 and have always been in beta state v1beta1 before they were removed with K8s version 1.25 (https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.25.md#podsecuritypolicy-is-removed-pod-security-admission-graduates-to-stable).

podSecurityPolicy is only listed within v1beta1 in the K8s API and not within v1:
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/

To Reproduce

Just run popeye version v0.11.0 against a cluster with e.g. version 1.24.7

Expected behavior

Results being displayed

Screenshots

none

Versions (please complete the following information):

OS: Ubuntu 22.04.1 LTS
Popeye: 0.11.0
K8s: v1.24.7+rke2r1

Additional context
none

@gargrag
Copy link

gargrag commented Feb 15, 2023

I just proposed a fix @shurkanTwo

@davidkmenta
Copy link

According to this issue — could you please leave old releases in the homebrew repository? Just in case to be able to downgrade the package. Thanks.

yalctay93 pushed a commit to mercedes-benz/popeye that referenced this issue May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants