Waldur Helm
Waldur is a platform for creating hybrid cloud solutions. It allows building enterprise-grade systems and providing self-service environment for the end-users.
Introduction
This chart bootstraps a Waldur deployment on a Kubernetes cluster using the Helm package manager.
Installing prerequisites
- Install Kubernetes server, for example, using minikube
- Install Kubernetes client, i.e. kubectl
- Install Helm
Installing the chart
-
Add the Waldur Helm repository
1
helm repo add waldur-charts https://waldur.github.io/waldur-helm/
-
Install dependencies or enable them in Helm values
Setup database using one of: - Simple PostgreSQL DB: instructions or - PostgreSQL HA DB: instructions or - Integrate with external DB: instructions
Install MinIO (for database backups): instructions
Install RabbitMQ for task queue: instructions
-
Install the Helm chart
1
helm install my-waldur waldur-charts/waldur -f path/to/values.yml
NB After this command, Waldur release will run in default
namespace.
Please, pay attention in which namespace which release is running.
For instance, you can install Waldur release
in test
namespace in the following way:
-
Create
test
namespace:1
kubectl create namespace test
-
Install release:
1
helm install waldur waldur --namespace test
However, postgresql release and waldur should be installed in the same namespace in order to share a common secret with DB credentials.
Adding admin user
Open waldur-mastermind-worker shell and execute the following command:
-
Get waldur-mastermind-worker pod name
1 2 3
# Example: kubectl get pods -A | grep waldur-mastermind-worker # --> # default waldur-mastermind-worker-6d98cd98bd-wps8n 1/1 Running 0 9m9s
-
Connect to pod via shell
1 2
# Example: kubectl exec -it deployment/waldur-mastermind-worker -- /bin/bash
-
Execute command to add admin user
1
waldur createstaffuser -u user -p password -e admin@example.com
Waldur Helm chart release upgrading
Delete init-whitelabeling job (if exists):
1 |
|
Delete load features job (if exists):
1 |
|
Upgrade Waldur dependencies and release:
1 2 |
|
Restart deployments to apply configmaps changes:
1 2 3 4 |
|
Private registry setup
A user can use private registry for Docker images.
For this, the corresponding credentials should be registered in a secret,
name of which should be placed in .Values.imagePullSecrets
.
A secret can be created trough CLI.
Configuration docs
Configuration documentation: index