The Dockerfiles use as builder in the FROM instruction which is not currently supported
by the RH's docker fork (see https://github.com/kubernetes-sigs/kubebuilder/issues/268).
One needs to run the imagebuilder command instead of the docker build.
Note: this info is RH only, it needs to be backported every time the README.md is synced with the upstream one.
For development purposes the powervs machine controller itself will run out of the machine API stack.
Otherwise, docker images needs to be built, pushed into a docker registry and deployed within the stack.
To deploy the stack:
kustomize build config | kubectl apply -f -
Deploy secret with Power VS credentials
Power VS nodeupdate controller assumes existence of a secret file:
You can use examples/render-powervs-secrets.sh script to generate the secret:
# Set the IBMCLOUD_API_KEY with a proper IBM Cloud API Key
$ IBMCLOUD_API_KEY=<API_KEY> ./examples/render-powervs-secrets.sh examples/addons.yaml | kubectl apply -f -
Deployed machine API plane (machine-api-controllers deployment) is (among other
controllers) running machine-controller. In order to run locally built one,
simply edit machine-api-controllers deployment and remove machine-controller container from it.
Build and run powervs actuator from outside the cluster
$ go build -o bin/machine-controller-manager github.com/openshift/machine-api-provider-powervs/cmd/manager
Package v1alpha1 contains API Schema definitions for the powervsproviderconfig v1alpha1 API group +kubebuilder:object:generate=true +groupName=powervsproviderconfig.openshift.io
Package v1alpha1 contains API Schema definitions for the powervsproviderconfig v1alpha1 API group +kubebuilder:object:generate=true +groupName=powervsproviderconfig.openshift.io