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
[FR] Add flag/config feature to allow users to get renderered manifest or some information about the resulting namespace of render + deploy config
#8191
Closed
aaron-prindle opened this issue
Dec 5, 2022
· 0 comments
· Fixed by #8309
Issues tracks adding flag/config feature to allow users get a renderered manifest or some information about the resulting namespace of render + deploy config.
Option 1 - (Skaffold) Render flag that populates the Namespace configured in deploy stanza
If there is a reason not to change the default behavior for render to support this, then a flag could be introduced on skaffold render to support it.
Option 2 - (Skaffold) Dry run
Introduce the ability to dry run skaffold apply where the output is the resources that would be applied to the cluster. Cloud Deploy could then inspect the dry run resource to extract the namespace that is being used at deploy time. Could be built on top of kubectl apply dry-run capability.
The text was updated successfully, but these errors were encountered:
aaron-prindle
changed the title
[FR] Add flag/config feature to allow users get a renderered manifest or some information about the resulting namespace of render + deploy config
[FR] Add flag/config feature to allow users to get renderered manifest or some information about the resulting namespace of render + deploy config
Dec 14, 2022
Issues tracks adding flag/config feature to allow users get a renderered manifest or some information about the resulting namespace of render + deploy config.
Option 1 - (Skaffold) Render flag that populates the Namespace configured in deploy stanza
If there is a reason not to change the default behavior for render to support this, then a flag could be introduced on skaffold render to support it.
Option 2 - (Skaffold) Dry run
Introduce the ability to dry run skaffold apply where the output is the resources that would be applied to the cluster. Cloud Deploy could then inspect the dry run resource to extract the namespace that is being used at deploy time. Could be built on top of kubectl apply dry-run capability.
The text was updated successfully, but these errors were encountered: