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
Currently when you apply a Kustomization or HelmRelease, your raw manifests are just the actual Kustomization object, alongside maybe sources, etc.
I think it would be highly valuable to be able to parse out the actual final rendered manifests in an "offline" method. So that one could validate the final set of manifests being applied to the cluster (or do debugging for helm charts and/or kustomizations), almost like just running kustomize build . or helm template .
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
-
Currently when you apply a Kustomization or HelmRelease, your raw manifests are just the actual Kustomization object, alongside maybe sources, etc.
I think it would be highly valuable to be able to parse out the actual final rendered manifests in an "offline" method. So that one could validate the final set of manifests being applied to the cluster (or do debugging for helm charts and/or kustomizations), almost like just running
kustomize build .
orhelm template .
Beta Was this translation helpful? Give feedback.
All reactions