Codefresh+Azure: DevOps, Kubernetes, Helm Webinar

Hello everyone! Today’s post will recap on our Codefresh+Azure webinar we had earlier today. Mainly, I want to help others who wish to quickly get up and running with the same demo I used during the live stream. Click here to watch the full webinar.

First, you can head on over to codefresh.io to create an account and get started. You can also head here to get started on Azure for free. Once you have accounts at both places, the rest of the blog post should be relatively easy to follow.

The GitHub repo I used can be found here – feel free to fork it so you can use it with your own Codefresh instance. Also, the funny basic container orchestration video can be relived as many times as you want via this link.

AKS Creation

Next, let’s create an AKS cluster in Azure. If you already have one, you can move on to the next step. The following commands via Azure CLI from your local system will create a resource group in your Azure subscription, create your AKS cluster in that resource group, and then grab the kube context needed to communicate with your Kubernetes cluster. You can also run the optional command to install kubectl onto your local system.

After you have your K8s (Kubernetes) cluster setup in Azure, you can add it into Codefresh under Account Settings > Integration > Kubernetes, or this link should take you to the correct page. From there, you would choose your provider, Microsoft Azure in this instance, and enter the necessary information. Codefresh provides a how-to link for how to get those credentials, but you can also click here for convenience.

Helm Install

Next, we need to install Helm on your local system so we can get Tiller (in cluster service for Helm) setup on your cluster. If you’re using a Mac and homebrew, simply run brew install kubernetes-helm  from your Terminal and helm should be installed on your CLI. Next, run helm init and tiller should deploy out to your K8s cluster.

Cool add-ons

In my demo I was using two different helm charts to handle the networking part of my croc-hunter web app. The two charts I use are kube-lego and nginx-ingress. Kube-lego uses let’s encrypt to create SSL certificates for my nginx-ingress. I then simply define my ingress hostname in my croc-hunter values.yaml file. When deployed, my croc-hunter app will actually use the nginx-ingress controller, which will send a request to my kube-lego pod, which will then produce an SSL certificate via let’s encrypt. Pretty neat. To get started with both of those charts, simply run the following two commands:

You will need to get the external IP address for the nginx-ingress-controller service. To do so, from your local command line run, kubectl get svc and hit enter. Once an External IP has been created for the service, you’ll see it under the external-ip column.

You will then need to add a DNS entry with your registrar provider and point it to the external ip of the ingress. You can hard code it or use a wildcard (more on wildcard entries in a future blog post).

In your codefresh.yml, (I have my example on GitHub), you will then want to update the custom_ingress_hostname with the DNS name you created.

The last thing you’ll want to do is create a namespace and secret for your release. You can automate this piece, but I think it will be best to show you how to do it manually as a learning objective.

You will need to get your username and password for your Codefresh registry. You can learn more about your Codefresh registry here. To start, go to Account Setttings > Integration > Docker Registry > Codefresh Registry to get your username and access token. Your “docker-server” as seen in the command below, should be r.cfcr.io. Rrun the below commands from your local command line.

Codefresh setup

Finally, you can import your forked version of my croc-hunter repo (which I just forked from Lachie Evenson [shoutout!]) and go from there. From the Codefresh dashboard, starting in Repositories, hit “add new” and then find your forked repo. Select it, hit next, and then hit the option that your repo has a codefresh.yml in it (because I added it). You might have to update things like the image name, kubecontext, custom_image, and  custom_ingress_hostname on both dev and master steps, but my example template should help you get started. You can also update all that information manually in crochunter-repo/charts/croc-hunter/values.yaml. (I use this repo for VSTS, Codefresh and Jenkins simultaneously, which is why I love that Codefresh allows me to override my values.yaml using their build and helm steps.)

When your codefresh.yml is setup with the information that’s specific to YOUR environment, you will have a full CI/CD dev/master branch pipeline for Codefresh, Azure (AKS), Kubernetes, and Helm. If you also followed the kube-lego and nginx-ingress controller steps earlier, your croc-hunter helm release should auto release into your pre-determined DNS A record with an SSL certificate to boot!

Finally, you can also schedule a 1:1 with Codefresh by clicking here and you can learn more about Azure AKS on our new docs page here.

Reminder: All of my posts are provided "AS IS", imply no warranties, and confer no rights or special privileges. Use of included postings, code samples and other works are subject to the terms specified at Microsoft. For more information, click here.

Comments 4

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.