A validate policy matches only `Pod` and uses a pattern on `metadata.namespace`. The author wants controller coverage through auto-generation. Why can this be a problem?

Question

Accepted Answer

A. Auto-generation rewrites the pattern under the Pod template, where that namespace path is not the intended controller field. The auto-gen documentation warns that patterns like `metadata.namespace` are translated under `spec.template.metadata` for controllers, which is not the desired field and can make controllers fail incorrectly. Option c is wrong because auto-generation absolutely supports validate rules; the issue here is path translation, not rule type.

A validate policy matches only `Pod` and uses a pattern on `metadata.namespace`. The author wants controller coverage through auto-generation. Why can this be a problem?

Related Questions

Discussion

A validate policy matches only Pod and uses a pattern on metadata.namespace. The author wants controller coverage through auto-generation. Why can this be a problem?

Related Questions

Discussion

A validate policy matches only `Pod` and uses a pattern on `metadata.namespace`. The author wants controller coverage through auto-generation. Why can this be a problem?