Persistent Volume
SonarQube will be making two PersistentVolumeClaims, one for SonarQube and one for the Postgres database. A PersistentVolume will be needed for each. Since this is all temporary in Katacoda, a hostPath based PersistentVolume is created for both.
mkdir -p /mnt/data/postgres && kubectl create -f pv-postgres.yaml
mkdir -p /mnt/data/sonarqube && kubectl create -f pv-sonarqube.yaml
Install
Create a namespace for the installation target.
kubectl create namespace sonarqube
Using Helm, install the SonarQube Helm chart with a few custom values.
helm install sonar stable/sonarqube --namespace sonarqube --values sonarqube-values.yaml
This chart bootstraps a SonarQube instance along with a PostgreSQL database. SonarQube also loads several plugins defined in the Helm chart configuration. To get a complete status of the deployment availability run this inspection.
watch kubectl get deployments,pods,services --namespace sonarqube
Once complete, the Pods will move to the running state. The deployment.extensions/sonar-sonarqube deployment may take 2-3 minutes before it reports `Available'. The behavior of the plugins can effect the startup time. All the Deployments will eventually move to the Available (1) state. Use this clear to break out of the watch or press Ctrl+C.
