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
Can someone tell why kustomize complains that the fieldPath .metadata.namespace is missing even though I set the "namespace" in my kustomization.yaml ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Can someone tell why kustomize complains that the fieldPath
.metadata.namespace
is missing even though I set the "namespace" in my kustomization.yaml ?I have a base kustomize with a single resource
I have a prod overlay that adds an ingress to the flink deployment
The "app", uses the prod overlay, adds a namespace, does a irrelevant patch to the spec and refers a component that alters the dns entry in ingress
The component is basically using "replacements" to alter the ingress
For some reason, kustomize is complaining that .medata.namespace does not exist. Even though in the app kustomization.yaml I've set the "namespace"
Am I missing something? The DNS subdomain HAS to be that of the provided namespace which is only known in the "app" kustomization
Beta Was this translation helpful? Give feedback.
All reactions