-
Epic
-
Resolution: Done
-
Major
-
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
- The following operator is created as one solution to this problem:
https://github.com/noseka1/gitops-friendly-machinesets-operator
Acceptance Criteria
- A path is defined on how to enable customers to manage MachineSets through GitOps workflows
- relates to
-
GITOPS-370 OpenShift cluster configuration using ArgoCD
- Closed