mongodb-operator | Kubernetes Operator that creates users | Database library

Create local Docker Registry. Start a local registry in Docker so you can run locally built images in the kubernetes cluster. Use the prepared configuration to create a local cluster with Kind and connect it to the registry. Kind will configure the context for the local cluster running on Docker. Install Kubernetes infrastructure components and wait until they are deployed.
Create local Docker Registry Start a local registry in Docker so you can run locally built images in the kubernetes cluster. $ docker run -d --restart=always -p "127.0.0.1:5000:5000" --name "kind-registry" registry:2 Unable to find image 'registry:2' locally 2: Pulling from library/registry ddad3d7c1e96: Pull complete 6eda6749503f: Pull complete 363ab70c2143: Pull complete 5b94580856e6: Pull complete 12008541203a: Pull complete Digest: sha256:bac2d7050dc4826516650267fe7dc6627e9e11ad653daca0641437abdf18df27 Status: Downloaded newer image for registry:2 71b8b621bf962a65a0b45b08731430be7b9c0f13ce540a19708be7cc3e325c56
Create Kubernetes cluster Use the prepared configuration to create a local cluster with Kind and connect it to the registry. Kind will configure the context for the local cluster running on Docker. $ kind create cluster --config=local/setup/mongodb-operator-cluster.yaml Creating cluster "mongodb-operator-cluster" ... ✓ Ensuring node image (kindest/node:v1.20.2) 🖼 ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✓ Starting control-plane 🕹️ ✓ Installing CNI 🔌 ✓ Installing StorageClass 💾 Set kubectl context to "kind-mongodb-operator-cluster" You can now use your cluster with: kubectl cluster-info --context kind-mongodb-operator-cluster Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂 $ kubectx -c kind-mongodb-operator-cluster $ docker network connect "kind" "kind-registry"
Install infrastructure Install Kubernetes infrastructure components and wait until they are deployed. $ kubectl apply -k kustomize/overlays/infra/ namespace/ingress-nginx created serviceaccount/ingress-nginx created serviceaccount/ingress-nginx-admission created role.rbac.authorization.k8s.io/ingress-nginx created role.rbac.authorization.k8s.io/ingress-nginx-admission created clusterrole.rbac.authorization.k8s.io/ingress-nginx created clusterrole.rbac.authorization.k8s.io/ingress-nginx-admission created rolebinding.rbac.authorization.k8s.io/ingress-nginx created rolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx created clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created configmap/ingress-nginx-controller created configmap/local-registry-hosting created service/ingress-nginx-controller created service/ingress-nginx-controller-admission created deployment.apps/ingress-nginx-controller created job.batch/ingress-nginx-admission-create created job.batch/ingress-nginx-admission-patch created validatingwebhookconfiguration.admissionregistration.k8s.io/ingress-nginx-admission created $ kubectl wait -n ingress-nginx --for=condition=ready pod -l=app.kubernetes.io/component=controller --timeout=90s pod/ingress-nginx-controller-6c74dd986c-vkjfv condition met It may be needed to remove the ValidatingWebhookConfiguration for the Ingress resource: $ kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission validatingwebhookconfiguration.admissionregistration.k8s.io "ingress-nginx-admission" deleted
Install MongoDB Install the MongoDB used for testing and check if the frontend is exposed. The web frontend is available at http://localhost. $ kubectl apply -k kustomize/overlays/mongodb/ namespace/mongodb created secret/mongodb-root-ttdd8k9hf6 created secret/mongoku-mongodb-admin-9g9g827kcc created service/mongodb created service/mongoku created deployment.apps/mongodb created deployment.apps/mongoku created ingress.networking.k8s.io/mongodb created $ curl -f -s http://localhost | grep "<title>" || echo "FAILED" <title>Mongoku</title> If the last command shows FAILED, usually the Mongoku frontend is still starting. This can be checked with: kubectl get -n mongodb pods
Build operator image To be used locally, the operator image must be pushed to the registry created above. $ ./gradlew jib -Djib.to.image=localhost:5000/mongodb-operator:local -Djib.allowInsecureRegistries=true > Task :jib Containerizing application to localhost:5000/mongodb-operator:local... Base image 'quay.io/sdase/openjdk-runtime:11-hotspot-distroless' does not use a specific image digest - build may not be reproducible The credential helper (docker-credential-desktop) has nothing for server URL: localhost:5000 Got output: credentials not found in native keychain Cannot verify server at https://localhost:5000/v2/. Attempting again with no TLS verification. Failed to connect to https://localhost:5000/v2/ over HTTPS. Attempting again with HTTP. Using base image with digest: sha256:c987f9fd30e233c4763a48cbf9d1164ac3eaf7ea01eda1f98d446cc8fcc33571 Container entrypoint set to [java, -cp, /app/resources:/app/classes:/app/libs/*, com.sdase.k8s.operator.mongodb.MongoDbOperator] Container program arguments set to [] Built and pushed image as localhost:5000/mongodb-operator:local Executing tasks: [==============================] 100,0% complete BUILD SUCCESSFUL in 7s 2 actionable tasks: 1 executed, 1 up-to-date
Install the operator Install the operator, check if the CRD is available and the operator is up and running. $ kubectl apply -k kustomize/overlays/operator/ customresourcedefinition.apiextensions.k8s.io/mongodbs.persistence.sda-se.com created $ kubectl get crd NAME CREATED AT mongodbs.persistence.sda-se.com 2021-06-07T15:54:40Z $ kubectl get -n mongodb-operator pods NAME READY STATUS RESTARTS AGE mongodb-operator-79bf4d9bd7-xxrql 1/1 Running 0 55s
Install a MongoDB database for testing Install the MongoDB as you would do when you need it for a service and check if the operator will provide a secret. $ kubectl kustomize kustomize/overlays/test/ apiVersion: v1 kind: Namespace metadata: name: local-test --- apiVersion: persistence.sda-se.com/v1beta1 kind: MongoDb metadata: name: local-test-db namespace: local-test spec: {} $ kubectl apply -k kustomize/overlays/test/ namespace/local-test created mongodb.persistence.sda-se.com/local-test-db created $ kubectl get -n local-test mongo NAME AGE test 33s $ kubectl get -n local-test secret TODO this needs to be implemented
Cleanup To value resources of your Docker installation, delete the local cluster and remove the registry. $ kind delete cluster --name mongodb-operator-cluster Deleting cluster "kind-mongodb-operator-cluster" ... $ docker stop kind-registry kind-registry $ docker rm kind-registry kind-registry