Feature Overview (aka. Goal Summary)  

Often customers use AWS tags in order to track usage and expenses of their internal teams. However, there are some resources that can only have their AWS tags be set at creation time or causing a roll out of all the nodes, which has workload impact.

This feature calls for being able to have the Admin persona (with permissions over Hosted Clusters and NodePools) be able to update the AWS tags on day 2 without causing a roll out.

Goals (aka. expected user outcomes)

Setting AWS tags on existing Hosted Clusters and their Nodepools happens without roll outs.

Requirements (aka. Acceptance Criteria):

Hosted Clusters as well as their nodepools and any resources created by HyperShift in setting them up are updatable in place.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Out of Scope

Change CAPI's tracking of resources.

Background

Follows up on OCPSTRAT-787

Documentation Considerations

Once this is available, the documented limitations in OCPSTRAT-787 should go away.

Interoperability Considerations

ROSA