![]()
####
Running Sitecore in the Azure Kubernetes Services (AKS), Nginx Ingress controller provides a public IP address that we can use to bind a hostname and root traffic to the environment. But in case of any update/redeploy of the ingress controller, the public IP address will be changed which means the website will be unavailable until DNS records are not updated. To avoid this website downtime we need to set up a static public IP address for the ingress controller.
There are two ways to create a public IP address within Azure Subscription:
- create a Public IP in a cluster’s resource group that is created within Kubernetes cluster;
- create a Public IP within any other Resource Group.
In first case we need to get a cluster’s resource group name. The following command can be used for that:
| *az aks show --resource-group **<Resource-Group-Name>** --name **<Kubernetes-Cluster-Name>** --query nodeResourceGroup -o tsv* |
| --- |
where *Resource-Group-Name* is a name of the resource group where our cluster is created. Usually the cluster’s resource group name looks like:
*MC\_**<Resource-Group-Name>\_<Kubernetes-Cluster-Name>\_<Cluster-Region>***
Then we need to create a Public IP using the following command:
| *az network public-ip create --resource-group MC\_**<Resource-Group-Name>\_<Kubernetes-Cluster-Name>\_<Cluster-Region>** --name **<IP-Address-Label-Name>** --sku Standard --allocation-method static* |
| --- |
In the second case the following command is used to create a static Public IP:
az network public-ip create --resource-group **<Resource-Group-Name>** --name **<IP-Address-Label-Name>** --sku Standard --allocation-method static
Then we need to ensure the cluster identity used by the AKS cluster has delegated permissions to the other resource group. For example:
| az role assignment create \
--assignee <Client ID> \
--role "Network Contributor" \
--scope /subscriptions/<subscription id>/resourceGroups/<resource group name> |
| --- |
To get a newly created IP we need to run the following command:
az network public-ip show --resource-group **<Resource-Group-Name>** OR MC\_**<Resource-Group-Name>\_<Kubernetes-Cluster-Name>\_<Cluster-Region>** --name **<IP-Address-Label-Name>** --query "{address: ipAddress}"
Once we have a Public IP address added, we need to add two additional lines to the install ingress controller command:
| helm install nginx-ingress ingress-nginx/ingress-nginx `
--set controller.replicaCount=2 `
--set controller.nodeSelector."beta\.kubernetes\.io/os"=linux `
--set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux `
--set controller.service.loadBalancerIP=<PUBLIC-IP-ADDRESS> `
--set controller.service.annotations."service\.beta\.kubernetes\.io/azure-dns-label-name"=<some-label> `
--set controller.admissionWebhooks.patch.nodeSelector."beta\.kubernetes\.io/os"=linux `
--set-string controller.config.proxy-body-size=10m |
| --- |
To make sure that everything is as expected, we can run a command below:
**kubectl get services**
The result of execution should look like following:
where EXTERNAL-IP should be the same as newly created. If you see <pending> instead, the following command can be useful for troubleshot:
***kubectl describe service nginx-ingress-ingress-nginx-controller***
###### 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 By Categories
[#E-commerce](https://www.brimit.com/blog?categories=#E-commerce)[#How-to](https://www.brimit.com/blog?categories=#How-to)[#Guides](https://www.brimit.com/blog?categories=#Guides)[Tech Talks](https://www.brimit.com/blog?categories=Tech%20Talks)[#OrderCloud](https://www.brimit.com/blog?categories=#OrderCloud)
###### More by Platform
[Data and AI](https://www.brimit.com/blog?platforms=Data%20and%20AI)[DXP](https://www.brimit.com/blog?platforms=DXP)[E-commerce](https://www.brimit.com/blog?platforms=E-commerce)[Internet of Things](https://www.brimit.com/blog?platforms=Internet%20of%20Things)[Sales and marketing automation](https://www.brimit.com/blog?platforms=Sales%20and%20marketing%20automation)
#### 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)
