Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8531

Enable AWS EC2 Tag configuration for Machine Pools during creation in the ROSA/OCM Web Console

XMLWordPrintable

    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Enable setting AWS resource tags when creating a ROSA Machine Pool in the OpenShift Cluster Manager (OCM) Web Console

      2. What is the nature and description of the request?

      Currently, AWS resource tags for ROSA worker nodes (EC2 instances created from a machine pool) can only be assigned during machine pool creation via the ROSA CLI, using the --tags option.

      The OCM web console does not expose this capability.
      Customers are unable to add AWS tags when creating a machine pool through the web UI, and the UI provides no field for setting spec.template.spec.providerSpec.value.tags.

      This RFE requests:

      • Adding UI support in the OCM Web Console to specify AWS EC2 tags at machine pool creation time.
      • Ensuring the UI functionality matches the capabilities of the CLI (rosa create machinepool --tags).
      • Validation of tag format and clear mapping to the MachineSet providerSpec.

      The RFE does not request support for modifying tags after creation (which is expected to remain unsupported).

      3. Why does the customer need this? (List the business requirements here)

      The customer is implementing AWS Service Control Policies (SCPs) that enforce mandatory tagging for cost allocation, compliance, FinOps, and resource governance across their AWS Production account.

      Impact:

      • Without required tags, resources created by ROSA (specifically EC2 worker nodes) may be blocked by SCP or non-compliant with cost management rules.
      • Machine pools created using the OCM UI cannot include mandatory tags, forcing the customer to use CLI-only workflows.
      • This breaks operational consistency, automation workflows, and governance standards.
      • Lack of UI support increases the risk of operational mistakes and hinders team adoption of ROSA.

      Business reasons for the feature:

      • Ensures ROSA clusters remain compliant with corporate tagging policies.
      • Eliminates cost allocation gaps in FinOps reporting.
      • Brings UI feature parity with CLI, reducing operational friction.
      • Supports customers with strict AWS governance frameworks.

      4. List any affected packages or components.

      • OpenShift Cluster Manager (OCM) Web Console
      • ROSA UI (console.redhat.com)
      • Machine Pool creation workflow
      • ROSA UX / AWS ProviderSpec for MachineSets

              rh-ee-adejong Aaren de Jong
              rhn-support-sdharma Suruchi Dharma
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None