• False
    • Hide


    • False
    • XCMSTRAT-36ARO - Using Managed Identity / Workload Identity to conform to least privilege
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • Program Call
    • Approved

      Feature Overview

      • Customers want to create and manage OpenShift clusters using managed identities for Azure resources for authentication.


      • A customer using ARO wants to spin up an OpenShift cluster with "az aro create" without needing additional input, i.e. without the need for an AD account or service principal credentials, and the identity used is never visible to the customer and cannot appear in the cluster.
      • As an administrator, I want to deploy OpenShift 4 and run Operators on Azure using access controls (IAM roles) with temporary, limited privilege credentials.


      • Azure managed identities must work for installation with all install methods including IPI and UPI, work with upgrades, and day-to-day cluster lifecycle operations.
      • Support HyperShift and non-HyperShift clusters.
      • Support use of Operators with Azure managed identities.
      • Support in all Azure regions where Azure managed identity is available. Note: Federated credentials is associated with Azure Managed Identity, and federated credentials is not available in all Azure regions.

      More details at ARO managed identity scope and impact.


      This Section: A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a requirement for ALL features. YES
      Release Technical Enablement Provide necessary release enablement details and documents. YES

      (Optional) Use Cases

      This Section:

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

      Questions to answer…

      • ...

      Out of Scope

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting need to know? What context can be provided to frame this feature.


      • ...

      Customer Considerations

      • ...

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content Strategy.
      • What concepts do customers need to understand to be successful in [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or Release Note)?


            julim Ju Lim
            julim Ju Lim
            Andrew Butcher, Dave Mulford, Derek Carr, Flavian Missi, Gregory Charot, Hemant Kumar, Hongan Li, James Harrington, Jerome Boutaud, Joel Speed, Ju Lim, Marcos Entenza Garcia, Michael Fisher, Miciah Masters, Mike Worthington, Mingxia Huang, Patrick Dillon, Wei Duan, xiujuan wang, Zhaohua Sun
            Andrew Butcher Andrew Butcher
            Mingxia Huang Mingxia Huang
            Stephanie Stout Stephanie Stout
            Scott Dodson Scott Dodson
            James Harrington James Harrington
            Lisa Lyman Lisa Lyman
            Dave Mulford Dave Mulford
            7 Vote for this issue
            31 Start watching this issue