Uploaded image for project: 'OpenShift Autoscaling'
  1. OpenShift Autoscaling
  2. AUTOSCALE-373

AutoNode should correctly tag all EC2 instances when running in an AWS Managed Service environment

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • AutoNode
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • AUTOSCALE - Sprint 278, AUTOSCALE - Sprint 279, AUTOSCALE - Sprint 280

      To comply with AWS managed policies, AutoNode should tag any EC2 instance that it creates with the red-hat-managed tag with the value 'true', when used as part of our AWS managed services e.g ROSA HCP. There are also other Red Hat tags that make sense to add to each EC2 instance

      Acceptance Criteria

      • Any EC2 instance launched by AutoNode in the context of our managed services should be tagged with the following:
        • 'red-hat-managed' with the value 'true'.
        • 'red-hat-clustertype' with the value 'rosa' for ROSA HCP
        • kubernetes.io/cluster/$CLUSTER_ID with the value 'owned'
      • If possible, can we remove the 'eks:eks-cluster-name' tag when running in a Red Hat context 

              jkyros@redhat.com John Kyros
              rblake@redhat.com Rob Blake
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: