Kubernetes
Step 1 - Prerequisites​
A local cluster. There are multiple options to run a local cluster:
caution
This local cluster is only required when you want to test the Kubernetes deployment on a local environment. If you have classic Kubernetes infrastructure, skip this first step and check the necessary additional configuration of Volumes, Networking, or General configuration.
info
This guide has been tested on minikube.
kubectl
, with a correct kubeconfig. Check your installation withkubectl version
.helm
cli. Check your installation withhelm version
.
Step 2 - Installation​
- Add the repo:
helm repo add exivity https://charts.exivity.com
info
If you had already added this repo earlier, run helm repo update
to retrieve
the latest versions of the packages.
- Verify the repo is added:
helm search repo exivity
- Create a namespace:
kubectl create ns exivity-quickstart
- Install the helm-chart:
helm install -n exivity-quickstart exivity-quickstart exivity/exivity --set licence=”you-very-long-licencekey”
Licence key
Reach out to us for a demo licence key.
tip
If you want to add dummy data to your deployment for testing purposes, you can add the following parameter to your command above:
--set service.dummyData.enabled=true
note
Take a look at the values.yaml file in case you want to customise certain components.
Step 3 - Verifying Installation​
Follow the official Kubernetes instructions to make sure ingress is working; for example on minikube this can be done with:
minikube addons enable ingress
Get the IP for your minikube instance by running:
minikube ip
Add a DNS record to your hosts file by appending the following to the file, replacing the IP with the result from the
minikube ip
command:0.0.0.0 exivity
Linux
On Linux, the hosts file is located at: /etc/hosts
Windows
On Windows, the hosts file is located at: C:\Windows\System32\drivers\etc\hosts
info
You might need admin rights to edit this file.
- Browse to exivity
- Log in using these credentials
username: admin
password: exivity
Removing Installation​
To uninstall the chart:
helm delete <chart-name>
To delete the PVCs (Persistent Volume Claims) associated with the release:
kubectl delete pvc -l app.kubernetes.io/instance=exivity