Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-10651

As a cluster admin, I want to be able to import my ROSA clusters automatically with no additional work beyond enabling the Discovery configuration.

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Critical Critical
    • MCE 2.6.0
    • ACM 2.11.0
    • Console
    • None
    • 2
    • False
    • None
    • False
    • eng-lead, devel-ack, ux-ack
    • Hide

      Provide the required acceptance criteria using this template.
      * Console can automatically import ROSA clusters
      * Console can display filtered list of ROSA clusters
      Show
      Provide the required acceptance criteria using this template. * Console can automatically import ROSA clusters * Console can display filtered list of ROSA clusters
    • ACM-639 - Discovery and import for managed OpenShift
    • No
    • ACM Console Sprint 254
    • Customer Facing, Customer Reported

      Value Statement

      MCE already discovers all OCM registered clusters and lists them on the console.  The discovery and foundation team have enhanced the discovery controller and import controller, to be able to import ROSA and ROSA-HCP clusters, when the DiscoveredCluster custom resource has its Spec.importAsManagedCluster, value set to TRUE.

      It was agreed to manage this key/value with a Policy where a user can configure whether they want to import all ROSA, ROSA-HCP or some filtered subset.  Examples: Filter on names, filter on labels, filter on some other key/value in the discoveredCluster custom resource.

      The customer could also build their own automation to set this key/value pair.

      Definition of Done for Engineering Story Owner (Checklist)

      • Discovery configuration page in the console explains how to enable the policy that will cause ROSA and/or ROSA-HCP clusters to be imported.
        • Options:
          • Link with an info icon
            • Documentation
            • Repo with the policy
            • etc...
          • Full Instructions on the configuration page
          • Instruction to read the manual
          • Details about the key/value pair with a link to instructions or the policy
          • Other ideas??

      Development Complete

      • The code is complete.
      • Functionality is working.
      • Any required downstream Docker file changes are made.

      Tests Automated

      • [ ] Unit/function tests have been automated and incorporated into the
        build.
      • [ ] 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • [ ] Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      Support Readiness

      • [ ] The must-gather script has been updated.

            rbrunopi Randy Bruno-Piverger
            jpacker@redhat.com Joshua Packer
            David Huynh David Huynh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: