{"id":1333,"date":"2018-04-23T01:29:03","date_gmt":"2018-04-23T08:29:03","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/aks-couchbase-kubernetes-operator\/"},"modified":"2018-04-23T01:29:03","modified_gmt":"2018-04-23T08:29:03","slug":"aks-couchbase-kubernetes-operator","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/pt\/aks-couchbase-kubernetes-operator\/","title":{"rendered":"AKS with the Couchbase Kubernetes Operator"},"content":{"rendered":"\n

AKS (Azure Container Service) is the managed Kubernetes service on Microsoft Azure<\/a>. It is currently in preview, so there are some things that may change down the road.<\/p>\n\n\n\n

In this post, I\u2019m going to create an AKS cluster and install a Couchbase cluster on it, using the Couchbase Kubernetes operator<\/a> (which is also in pre-release).<\/p>\n\n\n\n

This post assumes you\u2019ve already created an Azure account. If you haven\u2019t, check out Azure: Getting Started is Easy and Free<\/a>.<\/p>\n\n\n\n

Azure Cloud Shell<\/h2>\n\n\n\n

First, login to the Azure portal<\/a>. I\u2019m going to use a relatively new and very cool feature of Azure called the Cloud Shell. Click on the “command prompt” icon at the top right of the Azure portal screen.<\/p>\n\n\n\n

\"Azure<\/span><\/p>\n\n\n\n

Clicking this will open up a shell command prompt window right in your browser. The first time you do this, Azure will be prompt you to decide between Bash and PowerShell. I decided to use PowerShell. (If you are more comfortable with Bash, then you should still be able to follow along)<\/em>. You will need to setup a storage account the first time (and only the first time) you use the Cloud Shell. This will take several minutes.<\/p>\n\n\n\n

\"Bash<\/span><\/p>\n\n\n\n

Once you have a command prompt, you can start typing in commands directly to your browser!<\/p>\n\n\n\n

\"Azure<\/span><\/p>\n\n\n\n

If you\u2019re like me and have multiple account subscriptions within Azure (for instance, I have an MSDN subscription and a Pay-as-you-go subscription), you should check to see which is the “default” by entering this command:<\/p>\n\n\n

[crayon highlight decode=”true”]az account list<\/code>[\/crayon]<\/p>\n\n\n\n

This command will print out a list of your accounts in JSON format. Check out the isDefault<\/code> field in the JSON. For instance, mine had “Pay as you go” as the default (which I don\u2019t want, because I have plenty of credit on my MSDN account).<\/p>\n\n\n\n

If you want to change the default, enter a command like this:<\/p>\n\n\n

[crayon highlight decode=”true”]az account set --subscription \"Visual Studio Ultimate with MSDN\"<\/code>[\/crayon]<\/p>\n\n\n\n

You can use the subscription name (as I did) or the ID.<\/p>\n\n\n\n

Azure-cli<\/h2>\n\n\n\n

The above two commands that used “az” are using the “Azure CLI”. You can install this on your local machine, and it comes out-of-the-box when using the Cloud Shell.<\/p>\n\n\n\n

Before we can create a Kubernetes cluster with a Couchbase cluster, let\u2019s use azure-cli to lay the groundwork.<\/p>\n\n\n\n

First, create a resource group. A resource group is a logical grouping that you can use to organize the various services and instances in Azure. You can get a list of all your current resource groups with this command:<\/p>\n\n\n

[crayon highlight decode=”true”]az group list<\/code>[\/crayon]<\/p>\n\n\n\n

You can create a new resource group in a number of ways, but here\u2019s how you can do it from the command line:<\/p>\n\n\n

[crayon highlight decode=”true”]az group create --name cb_aks_spike --location eastus<\/code>[\/crayon]<\/p>\n\n\n\n

At this point, the resource group should appear when you run az group list<\/code>, or when you view your resource groups in the normal Azure Portal UI.<\/p>\n\n\n\n

If you\u2019re trying to use your local Windows PowerShell, you might also need to take the following steps:<\/p>\n\n\n\n

    \n
  1. Check to see if you have the ContainerService registered. You can find out by running az provider list | ConvertFrom-Json | Format-Wide<\/code> and seeing if it\u2019s listed there.<\/li>\n\n\n
  2. If it\u2019s not listed, start ContainerService registration: az provider register -n Microsoft.ContainerService<\/code><\/li>\n\n\n
  3. Then, monitor the progress of ContainerService registration: az provider show -n Microsoft.ContainerService<\/code> (wait until “registrationState” is not “Registering” and becomes “Registered”)<\/li>\n\n<\/ol>\n\n\n\n

    These steps might not be necessary when AKS goes out of preview into a general release.<\/p>\n\n\n\n

    Create AKS cluster<\/h2>\n\n\n\n

    Next, create an AKS cluster inside of the resource group you created in the previous section:<\/p>\n\n\n

    [crayon highlight decode=”true”]az aks create --resource-group cb_aks_spike --name cbAKScluster --generate-ssh-keys<\/code>[\/crayon]<\/p>\n\n\n\n

    (AKS cluster name can only contain letter, numbers, and dashes).<\/em><\/p>\n\n\n\n

    This will take some time to complete. When it\u2019s done, you\u2019ll have a managed container service with:<\/p>\n\n\n\n