Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-1711

Managing MachineSets with GitOps

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • 1.7.0
    • None
    • None
    • None
    • R&D Managing MachineSets with GitOps
    • False
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Goal

      As a cluster admin, I want to manage the MachineSets on OpenShift using GitOps workflows so that I can recreate clusters or create multiple clusters with identical node setup.

      More details on adding MachineSets:
      https://docs.openshift.com/container-platform/4.9/machine_management/creating-infrastructure-machinesets.html#machineset-yaml-aws_creating-infrastructure-machinesets

      The challenge with MachineSets i that it's an object owned by the cluster and contains attributes that are cluster-specific. Since the name of the MachineSet is specific to one cluster, applying MachineSets from a Git repo to multiple clusters does not work out of the box:

      apiVersion: machine.openshift.io/v1beta1
      kind: MachineSet
      metadata:
        labels:
          machine.openshift.io/cluster-api-cluster: <infrastructure_id> 
        name: <infrastructure_id>-infra-<zone> 
        namespace: openshift-machine-api
      spec:
       ...
      

      Related Work

      Acceptance Criteria

      • A path is defined on how to enable customers to manage MachineSets through GitOps workflows

            jrao@redhat.com Jaideep Rao
            ssadeghi@redhat.com Siamak Sadeghianfar
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: