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

Importing a cluster to RHACM, Adding and removing a node using the ClusterInstance yaml

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

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

      Value Statement

      As a cluster Operator, I want to import a cluster to be managed by RHACM hub cluster.

      Once cluster is imported, I want to be able to : add nodes using the ClusterInstane yaml and gitops, then will be able to remove it or add and remove more nodes.

      There are scenario when a cluster or a few clusters are installed before adopting hub cluster and once hub cluster is ready, I want to be able to import those clusters as per above.

      Requirements: 

      • importing a cluster using ClusterInstance Manifest. 
      • Scaling up (Adding a node ) using ClusterInstance Manifest. 
      • Scaling down (removing a node) using ClusterInstance Manifest. 
      • Applying Policies
      • upgrading imported cluster to ensure that all ACM use cases properly work on an imported cluster
      • Writing QE Functional test cases for this feature if need be.

       

      Ensure the issue title clearly reflects the value of this user story to the
      intended persona. (Explain the "WHY")

      Definition of Done for Engineering Story Owner (Checklist)

      • importing a cluster using ClusterInstance Manifest. This is done : [ ACM-24929]
      • Scaling up (Adding a node ) using ClusterInstance Manifest. This is tested and is working
      • Scaling down (removing a node) using ClusterInstance Manifest. This has been not working.
      • Applying Policies
      • upgrading imported cluster to ensure that all ACM use cases properly work on an imported cluster
      • Writing QE Functional test cases if need be.

      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

      • [ ] Create an informative documentation issue using the Customer

      Portal Doc template that you can access from [The Playbook](

      https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

      and ensure doc acceptance criteria is met.

      • Call out this sentence as it's own action:
      • [ ] Link the development issue to the doc issue.

      Support Readiness

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

              Unassigned Unassigned
              lhalleb@redhat.com Lazhar Halleb
              None
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                None
                None