You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We found when gatekeeper validation/mutationwebhook has kube-system/kube-node-lease or any of them enabled a supported scope we are warned by gke as warning. For our autopilot cluster the issue is much more severe since it does not allow provide manual as well automatic patches by post install jobs to modify/patch these namespaces. so we have only option to use default k8s labels, like name based labels.
As of now we only use Release namespace as default excluded namespaces list. we need to enable support template it to add other namespaces as we need.
I think we already have the key for name and it's value as release.namespaces.
Would not it be duplicate key in label selector. Need to check , I did with exempting them fin using label namespace post install job, autopilot is easy it has mutation to patch these namespaces automatically.
I don't think it's an issue because matchExpressions takes a list, not a map. So I don't see an issue with reusing the key kubernetes.io/metadata.name here with a list of additional namespaces to exempt.
We found when gatekeeper validation/mutationwebhook has kube-system/kube-node-lease or any of them enabled a supported scope we are warned by gke as warning. For our autopilot cluster the issue is much more severe since it does not allow provide manual as well automatic patches by post install jobs to modify/patch these namespaces. so we have only option to use default k8s labels, like name based labels.
As of now we only use Release namespace as default excluded namespaces list. we need to enable support template it to add other namespaces as we need.
Environment:
kubectl version
): v1.27.3 GKEThe text was updated successfully, but these errors were encountered: