Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-26041 (Azure Cloud) Configure CCLM e2e environment + Jenkins pipeline
  3. ACM-30198

(Azure Cloud) Deploy hub + 2 managed clusters with unique CIDRs and D8s_v3 workers

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • ACM Console Train 37 - 1

      Deploy a fresh set of Azure cloud clusters for CCLM testing:

      • 1 hub cluster (ACM + MCE)
      • 2 managed clusters with CNV + MTV

      Key requirements:

      • Non-overlapping CIDRs between managed clusters (see parent story for values)
      • Worker instance type: Standard_D8s_v3 (8 CPU, 32GB) or larger
      • Use openshift-install IPI with custom install-config.yaml to set CIDRs at install time
      • Preserve the metadata.json output for each cluster (needed by subctl cloud prepare azure – see MachineSet template)

      CIDR allocation:

        Managed 1 Managed 2
      clusterNetwork 10.128.0.0/14 10.132.0.0/14
      serviceNetwork 172.30.0.0/16 172.32.0.0/16
      machineNetwork 10.0.0.0/16 10.1.0.0/16

      (Per Submariner Azure Quickstart and CCLM Network Guide)

      Why fresh deployment:
      The existing Azure env (investigated Feb 2026) has identical CIDRs on both spokes and D2s_v3 workers – both are set at install time and cannot be changed post-deployment.

              rhn-support-ashafi Atif Shafi
              rhn-support-ashafi Atif Shafi
              David Huynh David Huynh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: