With our Storage Class configured we then need to create our jenkins setup. To
do this we’ll just use the helm cli with a couple flags.
In a production system you should be using a values.yaml file so that you can
manage the drift as you need to update releases
helm install stable/jenkins --set rbac.create=true,master.servicePort=80,master.serviceType=LoadBalancer --name cicd
The output of this command will give you some additional information such as the
admin password and the way to get the host name of the ELB that was
provisioned.
Let’s give this some time to provision and while we do let’s watch for pods to boot.
kubectl get pods -w
You should see the pods in init, pending or running state.
Once this changes to running we can get the load balancer address.
export SERVICE_IP=$(kubectl get svc --namespace default cicd-jenkins --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
echo http://$SERVICE_IP/login
This service was configured with a LoadBalancer so, an AWS Elastic Load Balancer (ELB) is launched by Kubernetes for the service. The EXTERNAL-IP column contains a value that ends with “elb.amazonaws.com” - the full value is the DNS address.
When the front-end service is first deployed, it can take up to several minutes for the ELB to be created and DNS updated. During this time the link above may display a “site unreachable” message. To check if the instances are in service, follow this deep link to the load balancer console. On the load balancer select the instances tab and ensure that the instance status is listed as “InService” before proceeding to the jenkins login page.