Skip to content

Commit be0a668

Browse files
fix(installer): drop labeler Job hook in favour of caller-applied Namespace
The pre-install Job approach (added in c0b76b1, b46151a) hits a fatal chicken-and-egg on Talos clusters that enforce PodSecurity baseline:latest on bare namespaces: pods "cozy-system-labeler-..." is forbidden: violates PodSecurity "baseline:latest": host namespaces (hostNetwork=true) The labeler needs hostNetwork=true (no CNI yet) which requires the namespace to be PSA-privileged, but the labeler's whole job is to add that label. Cannot work from inside the namespace it's labeling. Drop the labeler Job + ServiceAccount + ClusterRole + ClusterRoleBinding. The chart now only removes the chart-defined Namespace and assumes the caller pre-creates cozy-system with the right labels — same pattern as kube-prometheus-stack, argo-cd, cert-manager, and other mainstream charts. Install procedure becomes two-step: kubectl apply -f - <<EOF apiVersion: v1 kind: Namespace metadata: name: cozy-system labels: cozystack.io/system: "true" cozystack.io/deletion-protected: "true" pod-security.kubernetes.io/enforce: privileged EOF helm upgrade installer packages/core/installer \ --install --namespace cozy-system ... The cozystack-operator pod (hostNetwork=true) is then admitted because the namespace already has enforce=privileged. Verified end-to-end on a kind cluster — clean install in 0.1s, no hooks involved, no PSA conflict, no retry needed. Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 4754f57 commit be0a668

1 file changed

Lines changed: 0 additions & 111 deletions

File tree

‎packages/core/installer/templates/cozy-system-labels.yaml‎

Lines changed: 0 additions & 111 deletions
This file was deleted.

0 commit comments

Comments
 (0)