####
According to the Installation Guide for a Sitecore Production Deployment with Kubernetes, we have to use external services for SQL service, Solr cloud, and Redis cache. While the documentation describes how to initialize data for the SearchStax provider for Solr, it says nothing about how to configure Sitecore to use services such as Azure SQL with Elastic Pool and Azure Redis. This article describes what needs to be done.
#### Azure SQL with Elastic Pool
Once we have Kubernetes Cluster and Azure SQL installed, we need to allow them to communicate with each other. First of all, subnet should be added to **vNet**:
1. Go to the Resource Group where you have AKS installed, find your Virtual network definition and open it:
2. In the left sidebar find **Subnets**, open it and add a new one:
**Make sure that Microsoft.Sql is selected in the Services dropdown.**
3. Go to the Resource Group where you have **SQL server** installed, find and open it:
4. Copy **Server name, Server admin** and save somewhere. We will need it later.
5. Find Firewalls and virtual networks In the left side menu
1. Set Yes for Allow Azure services and resources to access this server.
2. Click + Add existing virtual network and select previously created subnet.
3. If you want to access SQL Service from your local machine or network, add a range of IP addresses to allow.
6. Go to the Resource Group where you have **Elastic Pool** installed, find and open it:
7. Copy **Elastic Pool Name**:
8. Now need to update our secrets:
1. Set **SQL Server name** copied earlier to the **sitecore-databaseservername.txt** secret (mssql is a secret default value)
2. Set **Server admin name** copied earlier to the **sitecore-databaseusername.txt** secret. It can be another user but with Admin permissions.
3. Set **Server admin password** to the **sitecore-databasepassword.txt** secret. The password is usually set during the SQL Server set up. You can also reset it in Azure Portal.
4. Set **SQL elastic pool name** copied earlier to the **sitecore-database-elastic-pool-name.txt** secret.
#### Azure Cache for Redis
There is only one connection string (for CM and CD roles) that needs to be updated to allow our Sitecore instance to use Redis Cache hosted in Azure. Once all our connection strings are managed in environment variables defined in k8s yaml files, we can simply change that. Variable that includes a Redis connection string called **Sitecore\_ConnectionStrings\_Redis.Sessions**. The default value looks like below:
We can update the connection string straight away in a yaml file still keeping that hardcoded, but I would like to suggest you add a new secret file and move the value there.
1. Go to the folder where your secrets are and add a new sitecore-redis-connection-string.txt file.
2. Open secrets customization.yaml file and add the following:
| - name: sitecore-redis
files:
- sitecore-redis-connection-string.txt |
| --- |
3. Open **cd.yaml** file and update the **Sitecore\_ConnectionStrings\_Redis.Sessions** environment variable:
| - name: Sitecore\_ConnectionStrings\_Redis.Sessions
valueFrom:
secretKeyRef:
name: sitecore-redis
key: sitecore-redis-connection-string.txt |
| --- |
4. Do the same for cm.yaml
5. Go to the Resource Group where you have **Azure Cache for Redis** installed, find and open it:
6. Copy its **Host name:**
****
6. Now need to update our secret file:
- Set the Host name copied above to the sitecore-redis-connection-string.txt secret.
6. Redeploy your secrets and cm,cd pods.
###### Author
[!\[artsiom-photo\](https://www.brimit.com/-/jssmedia/feature/blogs/authors/artsiom-200.jpg?h=202&iar=0&w=200&hash=41797D2540DF6EB6FDF558360F6F62B8)
Artsem Prashkovich
Sitecore MVP/ Solution Architect](https://www.brimit.com/blog/author?authors=Artsem%20Prashkovich)
#### More on Sitecore
[!\[How Vercel Will Help You Save Effort When Deploying Sophisticated Sitecore Projects\](https://www.brimit.com/-/jssmedia/project/brimit/blog/2024/vercel_cover-image.png)
#Guides#How-toDXPE-commerce
##### How Vercel Will Help You Save Effort When Deploying Sophisticated Sitecore Projects
Optimize and accelerate the development and deployment of complex multisite Sitecore projects.
Alexei Vershalovich on July 17, 2024](https://www.brimit.com/blog/how-vercel-will-help-you-save-effort-when-deploying-sophisticated-sitecore-projects)
[!\[Training Up Tomorrow's Sitecore MVPs: a Mentoring Success Story\](https://www.brimit.com/-/jssmedia/project/brimit/blog/2023/sitecore-mentoring---cover-image.png)
#How-toDXP
##### Training Up Tomorrow's Sitecore MVPs: a Mentoring Success Story
How to participate in the Sitecore Mentor program and help younger colleagues jump-start a career in Sitecore development.
Sergey Baranov on October 2, 2023](https://www.brimit.com/blog/training-up-tomorrows-sitecore-mvps)
[!\[Going Headless. Part 2: When a Headless CMS Is Your Best Bet (if you have Sitecore)\](https://www.brimit.com/-/jssmedia/project/brimit/blog/2022/headless/adobestock_456986731.jpg)
#How-toDXPE-commerce
##### Going Headless. Part 2: When a Headless CMS Is Your Best Bet (if you have Sitecore)
Discover how a headless CMS can benefit organizations that use Sitecore.
Daniil Raschupkin, Palina Trokhautsava on September 15, 2022](https://www.brimit.com/blog/going-headless-part-2-when-a-headless-cms-is-your-best-bet-if-you-have-sitecore)
