Uploaded image for project: 'OpenShift CFE'
  1. OpenShift CFE
  2. CFE-177

Update Infrastructure CRD in openshift/api

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • None
    • installer
    • 3
    • False
    • False
    • OCPPLAN-8154 - Apply user defined tags to all resources created by OpenShift (AWS)
    • CFE Sprint 212, CFE Sprint 213, CFE Sprint 214, CFE Sprint 215, CFE Sprint 216, CFE Sprint 217
    • 0

    Description

      After CFE-52, we should be clear on what API changes are necessary to make this feature GA.

      Likely outcome is that we need to move the tags from the Infrastructure status to the spec field, to signal that this is customizable during Day2 Operations. This needs to be done in a backward compatible manner, so the status tags should remain there as deprecated with the installation tags that were initially supplied.

      AC:

      • Create a PR to openshift/api with the agreed schema changes from CFE-52
      • Update the Installer to populate the new schema

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-346 Update openshift/api package version in cluster-config-operator

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-67 Make the resource tags on the image registry operator updatable

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-68 Make user defined resource tags on EC2 instances updatable

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-71 Make user defined resource tags on AWS EFS resources updatable

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-273 AWS PlatformSpec in Infrastructure CR should be updated with user provided tags

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          GitHub openshift/kubernetes#1232: CFE-177 - Admission Control for Infrastructure CR

          Activity

            People

              tgeer@redhat.com Trilok Geer
              tjungblu@redhat.com Thomas Jungblut
              Sherine Khoury
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: