{"id":3653,"date":"2020-12-12T13:34:37","date_gmt":"2020-12-12T13:34:37","guid":{"rendered":"https:\/\/www.robhabraken.nl\/?p=3653"},"modified":"2021-07-01T09:08:55","modified_gmt":"2021-07-01T09:08:55","slug":"paas-to-aks-an-overview","status":"publish","type":"post","link":"https:\/\/www.robhabraken.nl\/index.php\/3653\/paas-to-aks-an-overview\/","title":{"rendered":"PaaS to AKS: an overview"},"content":{"rendered":"\n

This blog post is part of a series about building a production ready Continuous Integration setup for Sitecore using K8s containers on AKS. For more information and other articles on this subject check out the series index<\/a>.<\/em><\/p>\n\n\n\n

Setting up a new environment from A to Z<\/h2>\n\n\n\n

Going over a complete provisioning, installation and deployment of a Sitecore container deployment to AKS, I have noticed that the process contains a lot of steps that have dependencies on earlier steps in the process, making the order very important, but also confusing because there are so many small tasks to take into account. That’s why I decided to go over the entire process of setting up a new environment, documenting each step along the way, to create a good foundation for further automation of the provisioning and deployment process. Again, pursuing a full Infrastructure-as-Code setup, while documenting any necessary manual configurations.<\/p>\n\n\n\n

In this overview I am using the scripts and ARM templates as provided in my repository https:\/\/github.com\/robhabraken\/paas-to-aks<\/a>, and as described in the previous blog post<\/a> of this series.<\/p>\n\n\n\n

Preparation<\/h3>\n\n\n\n

Maybe I’m stating the obvious here, but in order to be complete, let’s start by creating an Azure account and DevOps instance if you do not already have one. Also, we need to set up a repository and download the appropriate files.<\/em><\/p>\n\n\n\n

1.<\/strong> Create an Azure account<\/p>\n\n\n\n

2.<\/strong> Create an Azure DevOps project<\/p>\n\n\n\n

3.<\/strong> Create an Azure service connection from your DevOps project to your Azure subscription using the automatic Service principal creation:<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

4.<\/strong> Fork and clone my repository<\/a>, download the Container Deployment files<\/a> from Sitecore and populate the K8s directories<\/a> accordingly:<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

5.<\/strong> Fix the hard-coded Redis connection string in the K8s specification files as provided by Sitecore. For an explanation on how to do this, read the “Fixing the hard-coded Redis connection” section of my previous blog post<\/a>.<\/p>\n\n\n\n

Manual configuration<\/h3>\n\n\n\n

Now we need to do some manual configuration. First, we will provision a Key Vault instance, because that is used and referenced by multiple ARM templates. Secondly, we are going to configure the parameters of our ARM scripts so we can run them later on.<\/em><\/p>\n\n\n\n

6.<\/strong> Set the servicePrincipalId<\/code> in the keyvault.parameters.json file of the Key Vault ARM template<\/a> to the ID of the Service Principal created in step 3<\/p>\n\n\n\n

7.<\/strong> Provision the Key Vault using the .\\deploy.ps1 script provided with that template<\/p>\n\n\n\n

8.<\/strong> Update all parameter files used by the ARM templates with the subscription ID and the Key Vault reference. The \"keyVault\".\"id\"<\/code> within the parameter file should be formatted like this:<\/p>\n\n\n\n

\/subscriptions\/00000000-0000-0000-0000-000000000000\/resourceGroups\/{resource-grou-name}\/providers\/Microsoft.KeyVault\/vaults\/{keyvault-name}<\/pre>\n\n\n\n
There are only two parameter files that need to be configured:<\/p>\n\n\n\n