We require guidance in building application gateway from scratch

Question

We require guidance in building application gateway from scratch

Domagoj Leder 0

Hi team,

We are building a new environment in the cluster and we have manually created an ingress- application gateway instead of using helm.

Now issues we face are on the pods level, when pods destroy and create themselves for certain services, the new IP is not reflected in the ingress- application-gateway for that test environment. Requires manual intervention and configuration.

We plan on destroying this app gateway and raising new one via helm but would like guidance steps on what to watch out and how to configure it.

Domagoj Leder 0 Reputation points

2023-12-13T15:37:36.5466667+00:00

Thanks in advance.
Regards

Dom
Domagoj Leder 0 Reputation points

2023-12-15T09:15:32.2+00:00

Ok, thank you for your reply. Previously STG was build the way that app gateway was deployed via the azure portal on k8 service and than configured via helm. Is that the right method to follow?
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-15T09:49:11.62+00:00
Hello Domagoj Leder,

Thankyou for responding back.

Yes, you can deploy Azure Application Gateway on Kubernetes Service and configure it via Helm.

You can follow the steps below to deploy Azure Application Gateway on Kubernetes Service and configure it via Helm.

Create an Azure Application Gateway instance in the Azure portal.

Deploy the Azure Application Gateway Ingress Controller (AGIC) using Helm.

You can use the following command to deploy AGIC:

helm repo add application-gateway-kubernetes-ingress https://appgwingress.blob.core.windows.net/ingress-azure-helm-package/

helm repo update

helm install ingress-azure application-gateway-kubernetes-ingress/ingress-azure --set appgw.name=<appgw_name> --set appgw.resourceGroup=<appgw_resource_group> --set appgw.subscriptionId=<appgw_subscription_id> --set appgw.usePrivateIP=false --set armAuth.type=servicePrincipal --set armAuth.secretJSON=<secret_JSON> --set rbac.enabled=true

Replace <appgw_name>, <appgw_resource_group>, <appgw_subscription_id>, and <secret_JSON> with the appropriate values.

Create an ingress resource to route traffic to your Kubernetes Service.

You can use the following example:

apiVersion: extensions/v1beta1 kind: Ingress metadata: name: example-ingress annotations: kubernetes.io/ingress.class: azure/application-gateway appgw.ingress.kubernetes.io/use-private-ip: "false" spec: rules: - host: example.com http: paths: - path: /path backend: serviceName: <service_name> servicePort: <service_port>

Replace <service_name> and <service_port> with the appropriate values.

Hope this helps you.
Domagoj Leder 0 Reputation points

2023-12-18T08:18:24.88+00:00

Thank you very much Anveshreddy Nimmala. We will try this today and let you know on the outcome.
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-18T08:57:26.39+00:00

Hello Domagoj Leder,

Thankyou , please try and let me know if you need further help on this.
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-20T04:48:17.87+00:00

Hello Domagoj Leder,

I haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Domagoj Leder 0 Reputation points

2023-12-20T16:07:50.6933333+00:00

Hi Anveshreddy Nimmala,

We reached a little roadblock. What we are trying to achieve is deploy azure application gateway for the first time. We already have an ingress-controller deployed. We need Azure Application gateway deploy script.

We are at the step of configuring values file to run the helm install. The error we are getting goes:
"Error: INSTALLATION FAILED: Unable to continue with install: IngressClass "azure-application-gateway" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "my-app-gateway"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default""

We also tried from the Azure UI Portal- kubernetes cluster - networking to create Application gateway but got the following error as well:
Screenshot 2023-12-20 170420.png

To circle back, we are kindly asking steps to create application-gateway where we already have ingress-controller deployed on this environment.

Thanks in advance.
Dom

Anveshreddy Nimmala 3,560 Moderator

Hi Domagoj Leder,

Sure please follow below steps.

1.Create a Application Gateway in Azure using portal / Azure CLI

Update Your ingress resources to use Application Gateway.

kubernetes.io/ingress.class: azure/application-gateway

3.This annotation specifies that the ingress resource should use the Azure Application Gateway as the ingress controller.

4.Later you have to create a backend pool for Application Gateway.

<span class=" active-doc-2" data-doc-items="2">az network application-gateway address-pool create<a href="#doc-pos=2" data-tag-index="1"></a></span> \
    --gateway-name myAppGateway \
    --name myBackendPool \
    --resource-group myResourceGroup

replace the values for `myAppGateway` and `myResourceGroup`

Last you need to add servers to the backend pool created.

<span class=" active-doc-2" data-doc-items="2">az network application-gateway address-pool address add<a href="#doc-pos=2" data-tag-index="1"></a></span> \    --gateway-name myAppGateway \    --pool-name myBackendPool \    --resource-group myResourceGroup \    --address myServer1 \    --address myServer2

Hope this helps you.

Domagoj Leder 0 Reputation points

2023-12-22T08:37:08.0133333+00:00

Thanks. We are following the above guidance steps.
Domagoj Leder 0 Reputation points

2023-12-22T08:55:51.0066667+00:00

Hi , Anveshreddy Nimmala

Quick question. Step 1 - when we ticked Application Gateway ingress controller in networking/ on cluster we get the following error. We escalated with our Admin in regards the permissions but wanted to check with you here.

MicrosoftTeams-image (2).png

Thanks in advance.

Regards

Dom
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-22T11:06:11.1+00:00

Hello Domagoj Leder,

Please check with Admin and get contributor access for resources and network contributor access to perform the action.

hope this helps you.
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-26T03:57:05.5466667+00:00

Hello Domagoj Leder,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help

1 answer

Your answer

Domagoj Leder 0 Reputation points

2023-12-13T15:37:36.5466667+00:00

Thanks in advance.
Regards

Dom
Domagoj Leder 0 Reputation points

2023-12-15T09:15:32.2+00:00

Ok, thank you for your reply. Previously STG was build the way that app gateway was deployed via the azure portal on k8 service and than configured via helm. Is that the right method to follow?
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-15T09:49:11.62+00:00

Hello Domagoj Leder,

Thankyou for responding back.

Yes, you can deploy Azure Application Gateway on Kubernetes Service and configure it via Helm.

You can follow the steps below to deploy Azure Application Gateway on Kubernetes Service and configure it via Helm.

Create an Azure Application Gateway instance in the Azure portal.

Deploy the Azure Application Gateway Ingress Controller (AGIC) using Helm.

You can use the following command to deploy AGIC:

helm repo add application-gateway-kubernetes-ingress https://appgwingress.blob.core.windows.net/ingress-azure-helm-package/

helm repo update

helm install ingress-azure application-gateway-kubernetes-ingress/ingress-azure --set appgw.name=<appgw_name> --set appgw.resourceGroup=<appgw_resource_group> --set appgw.subscriptionId=<appgw_subscription_id> --set appgw.usePrivateIP=false --set armAuth.type=servicePrincipal --set armAuth.secretJSON=<secret_JSON> --set rbac.enabled=true

Replace <appgw_name>, <appgw_resource_group>, <appgw_subscription_id>, and <secret_JSON> with the appropriate values.

Create an ingress resource to route traffic to your Kubernetes Service.

You can use the following example:

apiVersion: extensions/v1beta1 kind: Ingress metadata: name: example-ingress annotations: kubernetes.io/ingress.class: azure/application-gateway appgw.ingress.kubernetes.io/use-private-ip: "false" spec: rules: - host: example.com http: paths: - path: /path backend: serviceName: <service_name> servicePort: <service_port>

Replace <service_name> and <service_port> with the appropriate values.

Hope this helps you.
Domagoj Leder 0 Reputation points

2023-12-18T08:18:24.88+00:00

Thank you very much Anveshreddy Nimmala. We will try this today and let you know on the outcome.
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-18T08:57:26.39+00:00

Hello Domagoj Leder,

Thankyou , please try and let me know if you need further help on this.
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-20T04:48:17.87+00:00

Hello Domagoj Leder,

I haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Domagoj Leder 0 Reputation points

2023-12-20T16:07:50.6933333+00:00

Hi Anveshreddy Nimmala,

We reached a little roadblock. What we are trying to achieve is deploy azure application gateway for the first time. We already have an ingress-controller deployed. We need Azure Application gateway deploy script.

We are at the step of configuring values file to run the helm install. The error we are getting goes:
"Error: INSTALLATION FAILED: Unable to continue with install: IngressClass "azure-application-gateway" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "my-app-gateway"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default""

We also tried from the Azure UI Portal- kubernetes cluster - networking to create Application gateway but got the following error as well:
Screenshot 2023-12-20 170420.png

To circle back, we are kindly asking steps to create application-gateway where we already have ingress-controller deployed on this environment.

Thanks in advance.
Dom
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-21T04:10:17.5066667+00:00

Hi Domagoj Leder,

Sure please follow below steps.

1.Create a Application Gateway in Azure using portal / Azure CLI

Update Your ingress resources to use Application Gateway.

kubernetes.io/ingress.class: azure/application-gateway

3.This annotation specifies that the ingress resource should use the Azure Application Gateway as the ingress controller.

4.Later you have to create a backend pool for Application Gateway.

az network application-gateway address-pool create<a href="#doc-pos=2" data-tag-index="1"></a> \ --gateway-name myAppGateway \ --name myBackendPool \ --resource-group myResourceGroup

replace the values for `myAppGateway` and `myResourceGroup`

Last you need to add servers to the backend pool created.

az network application-gateway address-pool address add<a href="#doc-pos=2" data-tag-index="1"></a> \ --gateway-name myAppGateway \ --pool-name myBackendPool \ --resource-group myResourceGroup \ --address myServer1 \ --address myServer2

Hope this helps you.
Domagoj Leder 0 Reputation points

2023-12-22T08:37:08.0133333+00:00

Thanks. We are following the above guidance steps.
Domagoj Leder 0 Reputation points

2023-12-22T08:55:51.0066667+00:00

Hi , Anveshreddy Nimmala

Quick question. Step 1 - when we ticked Application Gateway ingress controller in networking/ on cluster we get the following error. We escalated with our Admin in regards the permissions but wanted to check with you here.

MicrosoftTeams-image (2).png

Thanks in advance.

Regards

Dom
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-22T11:06:11.1+00:00

Hello Domagoj Leder,

Please check with Admin and get contributor access for resources and network contributor access to perform the action.

hope this helps you.
Anveshreddy Nimmala 3,560 Reputation points Moderator

2023-12-26T03:57:05.5466667+00:00

Hello Domagoj Leder,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help

Answer 1

Hello Domagoj Leder,

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

Before destroying the existing application gateway, please make sure that you have a backup of the configuration settings.

You can use the Get-AzApplicationGatewayConfig cmdlet to export the configuration settings to a file.

Once you have the backup, you can proceed with the following steps to deploy a new application gateway using Helm:

Install Helm on your machine if you haven't already done so.

You can follow the instructions provided in the official Helm documentation.

https://helm.sh/docs/intro/install/

Add the Azure Application Gateway Helm repository to your Helm client:

helm repo add application-gateway-kubernetes-ingress https<a href="#doc-pos=2" data-tag-index="2"></a>://appgwingress.blob.core.windows.net/ingress-azure-helm-package/

Update the Helm repository

helm repo update

Create a values file with the configuration settings for your new application gateway. You can use the sample values file provided in the Helm repository as a starting point:

helm show values application-gateway-kubernetes-ingress/ingress-azure > values.yaml

Modify the values file to match your requirements.

You can refer to the official documentation for the available configuration options

https://learn.microsoft.com/en-us/azure/application-gateway/tutorial-ingress-controller-add-on-new

Install the Helm chart with the modified values file:

helm install my-app-gateway application-gateway-kubernetes-ingress/ingress-azure -f values.yaml

Replace my-app-gateway with the name you want to give to your new application gateway.

Verify that the new application gateway has been deployed successfully by checking the status of the Helm release:

helm status my-app-gateway

You can also check the status of the application gateway in the Azure portal.

hope this helps. Let me know if you have any further questions.

Share via

We require guidance in building application gateway from scratch

1 answer

Your answer