Ahoy relies on Helm to be installed.
Add helm repo:
helm repo add ahoy https://lsdopen.github.io/ahoy-helm
helm repo update
Customise the Ahoy installation by editing the values in values.yaml.
Example value files available at: https://github.com/lsdopen/ahoy-helm/tree/main/charts/ahoy
We are now ready to install Ahoy:
helm install ahoy --namespace ahoy --create-namespace --values values.yaml ahoy/ahoy
Note for GKE installation; you need to create a TLS secret and supply the secret name in the values file:
kubectl create secret tls ahoy-tls-secret -n ahoy --cert ahoy.crt --key ahoy.key
Hint: to create a self-signed certificate if you don't already have a certificate:
openssl req -newkey rsa:2048 -nodes -keyout ahoy.key -x509 -days 365 -out ahoy.crt
Similarly, if you are installing Keycloak and ArgoCd in GKE with Ingress enabled, you will need to create a secret for both as well:
kubectl create secret tls keycloak-tls -n ahoy --cert keycloak.crt --key keycloak.key kubectl create secret tls argocd-tls-certificate -n ahoy --cert argocd.crt --key argocd.key
Add helm repo:
helm repo add ahoy https://lsdopen.github.io/ahoy-helm
helm repo update
Create Ahoy project:
oc new-project ahoy --display-name="Ahoy" --description="Ahoy, your Kubernetes release management tool"
Customise the Ahoy installation by editing the values in values.yaml. You may want to enable a route instead of an ingress.
OpenShift restricts the use of UID by default.
To allow Postgres and Keycloak to start up you will need allow the anyuid SCC:
oc adm policy add-scc-to-user anyuid -z default -n ahoy
oc adm policy add-scc-to-user anyuid -z ahoy-keycloak -n ahoy
We are now ready to install Ahoy:
helm install ahoy --namespace ahoy --values values.yaml ahoy/ahoy
To delete Ahoy:
helm delete ahoy --namespace ahoy