2 minute read
As already mentioned, the Machine Controller Manager is designed to run as controller in a Kubernetes cluster. The existing source code can be compiled and tested on a local machine as described in Setting up a local development environment. You can deploy the Machine Controller Manager using the steps described below.
$ kubectl apply -f kubernetes/crds
⚠️ Modify the
Makefile
to refer to your own registry.
bin/machine-controller-manager
$ make build
$ make docker-image
$ make push
/kubernetes/deployment/out-of-tree/deployment.yaml
. This is done when you want your controller running outside the cluster to be managed from.$ kubectl apply -f kubernetes/deployment/out-of-tree/deployment.yaml
$ kubectl apply -f kubernetes/deployment/out-of-tree/clusterrole.yaml
$ kubectl apply -f kubernetes/deployment/out-of-tree/clusterrolebinding.yaml
Machine-controller-manager supports several configurable parameters while deploying. Refer to the following lines, to know how each parameter can be configured, and what it’s purpose is for.
To start using Machine Controller Manager, follow the links given at usage here.
Was this page helpful?