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

Support for SNO+1 provisioning with ZTP/GitOps with a single commit

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • GitOps
    • False
    • None
    • False
    • Not Selected
    • x86_64

      1. Proposed title of this feature request
      Support for SNO+1 provisioning with ZTP/GitOps with a single commit

      2. What is the nature and description of the request?
      The current procedure for provisioning an SNO+1 cluster with ZTP/GitOps requires a two-step approach: 1. push a commit to create the initial SNO cluster 2. following the creation of it, push another commit to add a worker node.

      This request is for the implementation of a simplified procedure which will allow the provisioning of an SNO+1 cluster in one step. This means that the partner will be able to define the SNO+1 cluster in the SiteConfig in the initial commit. The expectation is that the process of provisioning an SNO+1 should take less amount of time, compared to the existing method.

      3. Why does the customer need this? (List the business requirements here)
      SNO+1 is a topology widely used by telco partners.

      4. List any affected packages or components.

      RHACM
      GitOps/ZTP

            phuet1@redhat.com Philippe Huet
            dvassili@redhat.com Demetris Vassiliades
            Philippe Huet
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: