Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
When using managed clusters with workflow templates, only the managed cluster name is parameterizable[1]
[1]
What you expected to happen:
Being able to pass as parameters for the template the:
- subnetwork
- zone
- workerConfig (specifically the machine type)
Steps to reproduce:
- Create a workflow template with parameters and it will only allow you to specify the managed cluster name.
Other information (workarounds you have tried, documentation consulted, etc):