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.
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?
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.
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?