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.
- Connect to the remote kubernetes cluster where you plan to deploy the Machine Controller Manager using the kubectl. Set the environment variable KUBECONFIG to the path of the yaml file containing the cluster info.
- Now, create the required CRDs on the remote cluster using the following command,
$ kubectl apply -f kubernetes/crds.yamlMakefile to refer to your own registry.
- Run the build which generates the binary to
bin/machine-controller-manager
$ make build- Build docker image from latest compiled binary
$ make docker-image- Push the last created docker image onto the online docker registry.
$ make push- Now you can deploy this docker image to your cluster. A sample development file is given at. By default, the deployment manages the cluster it is running in. Optionally, the kubeconfig could also be passed as a flag as described in
/kubernetes/deployment/deployment.yaml. This is done when you want your controller running outside the cluster to be managed from.
$ kubectl apply -f kubernetes/deployment/deployment.yaml- Also deploy the required clusterRole and clusterRoleBindings
$ kubectl apply -f kubernetes/deployment/clusterrole.yaml
$ kubectl apply -f kubernetes/deployment/clusterrolebinding.yamlMachine-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.