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

Hatchery main pod doesn't pass pod- and containerSecurityContext to its spawned worker pods #7339

Open
mhatvani opened this issue Mar 10, 2025 · 0 comments

Comments

@mhatvani
Copy link

Hello,

Hatchery kubernetes pod doesn't pass the pod and containerSecurityContext to its spawned worker pods. This became an issue since we started to use platform with hardened kubernetes (they have stricter policies) in a restricted namespace.
CDS can be installed, but when we start a workflow it gets stuck immediately as the spawned worker pods created by the hatchery kubernetes cannot be created due to pod/container security violation.

Image

I debugged the issue and the pod and containerSecurityContext, which we have to set for restricted namespace doesn't get passed to the worker pods. Attached screenshot of the main (hatchery-kubernetes) pod and a spawned worker pod.

Is there any workaround or can you fix it in a next release?

Image
Image
Image
Image

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

No branches or pull requests

1 participant