README.md

THIS REPOSITORY IS OBSOLETE. CONTENT HAS BEEN MIGRATED ONTO Keleustes

Kubernetes Operator for Openstack HELM

Creation of openstackhelm-operator

Initialising the openstackhelm-operator

operator-sdk new openstackhelm-operator --skip-git-init

Coding the openstackhelm-operator

operator-sdk add api --api-version=openstackhelm.openstack.org/v1alpha1 --kind=OpenstackChart
git add deploy/crds/
git add pkg/apis/openstackhelm/
git add pkg/apis/addtoscheme_openstackhelm_v1alpha1.go
git add deploy/role.yaml

vi pkg/apis/openstackhelm/v1alpha1/*_types.go
operator-sdk generate k8s

operator-sdk add controller --api-version=openstackhelm.openstack.org/v1alpha1 --kind=OpenstackChart

Adjusting crds

Don't understand yet how to build using operator-sdk operator with the same level of detailes than controller-gen. Big hack that have to be included in Makefile.

go run vendor/sigs.k8s.io/controller-tools/cmd/controller-gen/main.go crd --output-dir ./chart/templates/
operator-sdk generate k8s

or

make generate

Compiling the openstackhelm-operator

make docker-build

Deploying

Deployment of operator using helm

helm install --name osh-operator chart 

Openstack Databases Backup CRD and Controller

Trigger a backup

Upon creation of the custom resource, the controller will

• Create a new workflow owned by the customer resource.
• Add events to the custom resources.
• The workflow creation will get argo to react and run the workflow, and create news pods.

kubectl create -f examples/openstackchart-testchart.yaml

Test controller reconcilation logic (for depending workflows)

Upon deletion of its workflow, the controller will recreate it, which will get argo to rerun the workflow.

Test controller reconcilation logic (for CRD)

When deleting the CRD, the corresponding workflow should be deleted. Argo in turn, will delete the corresponding pods.

kubectl delete -f examples/openstackchart-testchart.yaml