Spinnaker PoC Installation Instructions¶
Spinnaker + OpsMx Enterprise Spinnaker (OES) extensions.¶
Prequisites¶
- Kubernetes cluster 1.13 or later with at least 6 cores and 20 GB memory
- Helm is setup and initialized in your Kubernetes cluster. The following command should return both client and server version.
helm version
If helm is not setup, follow https://helm.sh/docs/using_helm/#install-helm to install helm. If you use the Google or Azure cloud shell, they already have helm installed on it. You can follow these three simple steps to initialize helm in the kubernetes cluster.
kubectl create serviceaccount -n kube-system tiller kubectl create clusterrolebinding tiller-binding --clusterrole=cluster-admin --serviceaccount kube-system:tiller helm init --service-account tiller --wait
-
Docker registry credentials is setup as a secret in Kubernetes, optionally specifying the namespace OES will be deployed to
kubectl create secret docker-registry oes-repo --docker-username=your_username --docker-password=your_password --docker-email=opsmx@example.com [--namespace mynamespace]
The namespace must exist before you run the command. If it does not exist,
kubectl create namespace mynamespace
If you name your secret something other than oes-repo, you need to update the key k8sSecret in values.yaml.
Before you install OES, please send an email to spinnaker-poc@opsmx.io requesting access to the Spinnaker images. We will provide the dockerhub username/password that you can use to access the image.
- Your Kubernetes cluster supports persistent volumes and loadbalancer service type
Deploying Spinnaker with OpsMx Enterprise Spinnaker (OES) Extensions¶
-
Clone the OpsMx Enterprise Spinnaker github repository
git clone https://github.com/OpsMx/enterprise-spinnaker.git
-
Go to enterprise-spinnaker/charts/oes and deploy the chart, optionally specifying the namespace
cd enterprise-spinnaker/charts/oes
helm install -n oes . [--namespace mynamespace]
Deploying OpsMx Enterprise Spinnaker (OES) Extensions on top of existing Spinnaker¶
The existing Spinnaker must be running in a Kubernetes cluster and OpsMx Enterprises Extensions should be deployed to the same namespace where Spinnaker is installed.
-
Clone the OpsMx Enterprise Spinnaker github repository
git clone https://github.com/OpsMx/enterprise-spinnaker.git
-
If Gate is accessible on a name other than spin-gate within the cluster, update spinnaker.baseurl property in enterprise-spinnaker/charts/oes/config/config.properties file to the correct value.
-
Go to enterprise-spinnaker/charts/oes and deploy the chart, optionally specifying the namespace where Spinnaker is already installed
cd enterprise-spinnaker/charts/oes helm install -n oes . --set installSpinnaker=false [--namespace mynamespace]
Connecting to Spinnaker and OpsMx Enterprise Enterprise Extensions¶
Connecting to Spinnaker¶
Once the service is up and running, find the service ip address
kubectl get svc spin-deck-np [--namespace mynamespace]
Example output would be:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE spin-deck-np LoadBalancer 192.168.1.1 192.168.1.1 9000:31030/TCP 8m9s
Using the EXTERNAL-IP address, go to http://EXTERNAL-IP:9000/
Connecting to OpsMx Enterprise Spinnaker Extensions(OES)¶
Once the service is up and running, find the service ip address
kubectl get svc oes [--namespace mynamespace]
Example output would be:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE oes LoadBalancer 192.168.1.1 192.168.1.1 8090:32097/TCP,8161:32527/TCP,9090:31265/TCP,8050:31094/TCP 9m11s
Using the EXTERNAL-IP address, go to http://EXTERNAL-IP:8161/
You can login with admin/OpsMx@123
You can change the default password during installation by updating the values.yaml or by adding this additional parameter to the helm install command:
--set openldap.adminPassword=myPassword