Description of problem:
As a user I want to be able to choose from different templates when creating a new project based on my roles/groups. From the UI and the CLI.
As an admin of OpenShift I want OpenShift to allow me to manage project templates upon roles/groups. Providing the possibility to define different sets of components and constraints.
Currently OpenShift only supports one template which is defined in the master-config.yaml it is an static configuration which needs to be propagated among masters.
For this reason, OpenShift needs to be able to dynamically gather the available project templates and allow users to chose which template they want to apply when creating a new project.
Pretty sure this is going to have to go to the platform team first, I doubt we have what we need from the backend to support this. @mfojtik WDYT?
To possibly add a little more context about what we're trying to achieve.
We're using annotations on the Projects to manage three things:
* Node Allocation
* Router Sharding (also tied to node allocation)
We don't want to give people the ability to change the annotations directly, since they could set them to things they shouldn't be set to. But we would like to be able to offer a set of Templates that they could chose from to select, for example:
* Does the project live in the 'internal' or 'external' zone?
* Does the project use their 'personal' quota, or a 'team' quota?
We probably wouldn't allow all possible combinations, since external zone access would probably be tied to a specific 'team' quota. So simply being able to pick from a limited set of templates is sufficient. Rather than being able to fully customise the new-project page.
This bug has been identified as a dated (created more than 3 months ago) bug.
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog,
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year.
As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed,
as it is currently not part of the products immediate priorities.
Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.