machine-api-operator

README

Machine API Operator

An Operator for managing the cluster-api stack and the Openshift owned machineSets:

• Aggregated API server
• Controller manager
• Machine controller (AWS/OpenStack/Libvirt actuator)

Manual deployment (for Kubernetes cluster)

When running the mao on the installer it assumes some existing resources that make it work as expected. To deploy the machine-api-operator in a vanilla kubernetes environment, one needs to precreate these assumptions:

• Create the openshift-machine-api-operator namespace
• Create the CRD Status definition
• Create the mao config
• Create the apiserver certs
• Create a given ign config
• You can run it as a deployment with this manifest
• Build:

  make build
  

• Run:

  ./bin/machine-api-operator --kubeconfig ${HOME}/.kube/config  --config tests/e2e/manifests/mao-config.yaml --manifest-dir manifests
  

• Image:

  make image
  

For running all this steps automatically check e2e test

CI & tests

e2e test in a vanilla Kubernetes environment

Tests are located in machine-api-operator repository and executed with make test in prow CI system. A link to failing tests is published as a comment in PR by @openshift-ci-robot. Current test status for all OpenShift components can be found in https://deck-ci.svc.ci.openshift.org.

CI configuration is stored in openshift/release repository and is split into 3 files:

• cluster/ci/config/prow/plugins.yaml - says which prow plugins are available and where job config is stored
• ci-operator/config/openshift/machine-api-operator/master.yaml - configuration for machine-api-operator component repository
• ci-operator/jobs/openshift/machine-api-operator/openshift-machine-api-operator-master-presubmits.yaml - prow jobs configuration for presubmits
• ci-operator/jobs/openshift/machine-api-operator/openshift-machine-api-operator-master-postsubmits.yaml - prow jobs configuration for postsubmits

More information about those files can be found in ci-operator onboarding file

Initial configuration for machine-api-operator CI pipeline can be found in PR #1095.