RFE: Allow customer to specify custom tags at installation time.
Background:
The ROSA (through the OpenShfift installer) tags the resources it creates with two tags:
key: Name Value: name of cluster
key" kubernetes.io/cluster/{cluster-name} Value =- owned
These tags apply to EC2 instances, EBS, LBs, etc
If an item is used but not created, eg deploying into an existing VPC then a shared tag is added, then later removed from the VPC.
Resource created later (new machine pools, LBs, etc) all get the same tags.
OpenShift supports allowing passing custom tags to the installer which will add those extra tags to the objects created at install time but does not guarantee that objects created post-installation will be tagged.
Openshift RFE 2012 along with a couple of others referenced in that RFE outline the path to fully support custom tags throughout the cluster's lifecycle.
RFE: Allow customer to specify custom tags at installation time.
Background: The ROSA (through the OpenShfift installer) tags the resources it creates with two tags: key: Name Value: name of cluster key" kubernetes.io/cluster/{cluster-name} Value =- owned These tags apply to EC2 instances, EBS, LBs, etc If an item is used but not created, eg deploying into an existing VPC then a shared tag is added, then later removed from the VPC. Resource created later (new machine pools, LBs, etc) all get the same tags.
OpenShift supports allowing passing custom tags to the installer which will add those extra tags to the objects created at install time but does not guarantee that objects created post-installation will be tagged. Openshift RFE 2012 along with a couple of others referenced in that RFE outline the path to fully support custom tags throughout the cluster's lifecycle.