This repository includes a deployment configuration for habitcentric using helmfile.
The configuration provides two environments with different deployment configurations:
Default environment
Deploys habitcentric using its own Spring API gateway and makes it accessible using a Kubernetes Ingress.
Istio environment
Deploys habitcentric without its Spring API gateway and makes it accessible using the Istio service mesh.
Linkerd environment
Deploys habitcentric without its Spring API gateway and makes it accessible using the Linkerd 2 service mesh.
Kuma environment
Deploys habitcentric without its Spring API gateway and makes it accessible using the Kuma service mesh.
- Running Kubernetes cluster
- Properly configured Kubernetes client
kubectl
to administrate your cluster - Locally installed helmfile CLI (version >= 0.9.3)
- Locally installed Helm CLI (version >= 3.0.0) with Helm Diff plugin (version >= 3.0.0-rc.7)
- Optional for Istio environment: Existing Istio installation on Kubernetes cluster
Detailed instructions on how to install Istio on your Kubernetes cluster and additional example configurations are located here. - Optional for Linkerd environment: Existing Linkerd installation on Kubernetes cluster
Detailed instructions on how to install Linkerd on your Kubernetes cluster and additional example configurations are located here.
helmfile apply
helmfile --environment istio apply
helmfile --environment linkerd apply
helmfile --environment kuma apply
Traefik Mesh does not support our current show-case. More information here
helmfile --environment traefik-mesh apply
helmfile destroy
helmfile --environment istio destroy
helmfile --environment linkerd destroy
helmfile --environment kuma destroy
helmfile --environment traefik-mesh destroy