-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feat: add seccompProfile #3562
feat: add seccompProfile #3562
Conversation
/run-e2e |
@zroubalik I can't find any details about e2e failure One thing to be aware of: seccompProfile is only supported in Kubernetes 1.19+ |
@joebowbeer that failure is transient, unrelated :) |
Could you please update Changelog to reflect this addition? |
f0bdd4f
to
262c10f
Compare
@zroubalik PTAL Since seccompProfile requires Kubernetes 1.19+ (otherwise validation fails), I think this is the best that can be done until the minimum version is raised from 1.17 to 1.19. |
As per https://github.com/kedacore/governance/blob/main/SUPPORT.md#kubernetes-support we should just add it given 1.19 has been out for a while. Adding something that is documented doesn't add much value given end-users will not notice that so it will not be used |
@zroubalik @tomkerkhove PTAL I restored the seccompProfile changes for Kubernetes 1.19+ that have already been merged into the helm chart. /run-e2e ? |
/run-e2e |
@JorTurFer @zroubalik the e2e tests failed in 0s - flake? |
yes, it looks as flaky test, I have opened an issue to review them #3594 |
Thanks for your contribution! |
/run-e2e ? |
/run-e2e |
hey @joebowbeer |
Could you rebase your PR? 🙏 after the release there is a conflict with the changelog |
Signed-off-by: Joe Bowbeer <[email protected]>
118d414
to
def1fda
Compare
@JorTurFer rebased |
/run-e2e |
Thanks a lot! ❤️ |
Add/update securityContext configs:
Checklist
Fixes #3561