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
I'm deploying an Argo WorkflowTemplate with Kustomize and the configMapGenerator generated name with the suffix does not get applied to my WorkflowTemplate. Is there a way to enable this or will Kustomize only make changes to K8s builtin resource?
My WorkflowTemplate contains an env property that sources from a ConfigMap.
Even though this is a custom type I would expect Kustomize to walk the manifest and find and replace any yaml block that matches up with a valid Kubernetes type, env/configMapKeyRef in this case.
The text was updated successfully, but these errors were encountered:
I'm deploying an Argo WorkflowTemplate with Kustomize and the configMapGenerator generated name with the suffix does not get applied to my WorkflowTemplate. Is there a way to enable this or will Kustomize only make changes to K8s builtin resource?
My WorkflowTemplate contains an
env
property that sources from a ConfigMap.The
config-api-exports
ConfigMap is generated by a configMapGenerator.Even though this is a custom type I would expect Kustomize to walk the manifest and find and replace any yaml block that matches up with a valid Kubernetes type, env/configMapKeyRef in this case.
The text was updated successfully, but these errors were encountered: