This request is modify the way deploy works to allow for more flexible workflows. Currently a user can use --local-images to generate the deployment role without having to also push the images to a registry. However, the deployment role is still hard coded to the image reference and registry.
The user stories I'd like to see considered as they will provide more flexibility:
1) Ability to generate or update deployment role without pushing or having images locally
2) Ability to have a deployment role that can be used no matter where my kube or openshift cluster is (e.g. turning registry into a variable, image references, etc.)
Some workflows to support:
1) storing a "generic" deployment role in source control
2) being able to generate or update deployment role independent of image building
3) being able to generate or update deployment role before spinning up a cluster
ISSUE TYPE
SUMMARY
This request is modify the way deploy works to allow for more flexible workflows. Currently a user can use
--local-imagesto generate the deployment role without having to also push the images to a registry. However, the deployment role is still hard coded to the image reference and registry.The user stories I'd like to see considered as they will provide more flexibility:
1) Ability to generate or update deployment role without pushing or having images locally 2) Ability to have a deployment role that can be used no matter where my kube or openshift cluster is (e.g. turning registry into a variable, image references, etc.)
Some workflows to support:
1) storing a "generic" deployment role in source control 2) being able to generate or update deployment role independent of image building 3) being able to generate or update deployment role before spinning up a cluster