What Does It Mean for the Application Gateway Ingress Controller (AGIC) to Assume “Full Ownership”?

Published Oct 19 2021 01:39 PM 1,106 Views
Microsoft

This article pulls from two key Microsoft documentation sources on installation of Application Gateway Ingress Controller (AGIC) which, if read individually, can be a bit confusing if both aren’t factored together. The articles are:

  1. Install an Application Gateway Ingress Controller (AGIC) using an existing Application Gateway
  2. Tutorial: Enable Application Gateway Ingress Controller add-on for an existing AKS cluster with an e...

The question we will tackle here is what does it mean in the documentation when we choose the "Brownfield" option for either Helm or the Ingress Controller Add-on where the documentation says, at least in the first article, that AGIC assumes “full ownership” of the Application Gateway it is associated with?

 

Basically, there are two ways to install AGIC on an existing Application Gateway:  Helm and the AGIC add-on option. Only the Helm install supports the multi-cluster/shared Application Gateway scenario, which must be explicitly specified as “true” since “false” is the default option. What this means is when shared is set to true, AGIC can support more than one AKS cluster and can also mix in other backends such as App Service or Virtual Machine Scale Sets. This may or may not be the best idea all depending. If the AGIC add-on option is used, currently there is no sharing the Application Gateway with other backends, and it does not support multiple AKS clusters, but the advantage is that it provides a fully managed experience and when AGIC is updated the add-on is automatically updated whereas with Helm any updates to AGIC must be performed manually. So if you’re going to install with Helm in the default mode, the AGIC add-on may be the better option as effectively it is the same thing but with the full managed experience.

 

The Helm installation documentation, in the Multi-cluster/Shared Gateway section, notes that with the  default option (not shared), AGIC will assume “full ownership” of the Application Gateway that AGIC is linked to (as does the AGIC add-on). What precisely does this mean? What it means is if you have an existing Application Gateway then any existing Backend pools, Http settings, Listeners, or Rules, when you deploy a workload to AKS with AGIC annotations, will either be deleted or rendered inoperative by default. And while the documentation presents a “brownfield” option for the AGIC add-on, it is actually not brownfield since it destroys whatever is already there, so do not use the AGIC add-on with an existing Application Gateway if you want to retain what configuration is already there. Below we will demonstrate what happens after AGIC is installed and subsequently an AKS application is deployed.

 

Below is a screenshot of two existing backend pools for two App Service applications:

 

walterm_0-1634061006361.png

 

Below are the Http settings for each of the two applications:

 

walterm_1-1634061042940.png

 

There are two listeners for the app on port 80, where the listener on port 80 performs a redirect to the listener on 443 (we will see this later with the AKS deployment). The second app uses https on port 8080.

 

walterm_2-1634061062721.png

 

Below are two rules for the first app tying the various listeners to their Http settings and backend pools (again, the defaultrule performs a redirect to the defaulthttpsrule). The other rule is for the second app.

 

walterm_3-1634061080859.png

 

Now let’s take a look at the sample Kubernetes manifest below that we will deploy leveraging AGIC, based on a common image in the Microsoft container registry. We have specified in annotations that we want to use AGIC, and we have specified our SSL certificate (which we added to Application Gateway previously using the az network application-gateway ssl-cert create command), and we have specified that we want SSL redirect (as discussed above).

 

apiVersion: apps/v1

kind: Deployment

metadata:

  name: aspnetapp-deployment

  labels:

    app: aspnetapp

spec:

  replicas: 3

  selector:

    matchLabels:

      app: aspnetapp

  template:

    metadata:

      labels:

        app: aspnetapp

    spec:

      containers:

      - image: "mcr.microsoft.com/dotnet/core/samples:aspnetapp"

        name: aspnetapp-image

        ports:

        - containerPort: 80

          protocol: TCP

 

---

 

apiVersion: v1

kind: Service

metadata:

  name: aspnetapp

spec:

  selector:

    app: aspnetapp

  ports:

  - protocol: TCP

    port: 80

    targetPort: 80

 

---

 

apiVersion: extensions/v1beta1

kind: Ingress

metadata:

  name: aspnetapp

  annotations:

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

    appgw.ingress.kubernetes.io/appgw-ssl-certificate: <name of your certificated added to Application Gateway>

    appgw.ingress.kubernetes.io/ssl-redirect: "true"

spec:

  rules:

  - http:

      paths:

      - path: /

        backend:

          serviceName: aspnetapp

          servicePort: 80

 

Once deployed, we can now see how AGIC has effectively taken ownership of the Application Gateway. The defaultaddresspool was stripped of its rules and targets, and the secondaddress pool has been deleted. AGIC then adds its own backend pool for our AKS deployment.

 

walterm_4-1634061110936.png

 

In Http settings, AGIC creates an entry for the AKS deployment, but leaves one of the existing Http settings and adds a probe to it, though it is not used for anything.

 

walterm_5-1634061134310.png

 

Now to the listeners. The existing listeners are all removed, and AGIC adds both a port 80 and 443 listener. As seen before, in the corresponding rules the port 80 listener will redirect to the 443 listener, which we specified in the above manifest with this annotation:

 

appgw.ingress.kubernetes.io/ssl-redirect: "true"

 

Below is a screenshot of our listeners after the AKS deployment.

 

walterm_6-1634061156196.png

 

Finally, regarding rules, it is rules that tie the front end listener with the backend Http settings and Backend pools. The existing rules are completely replaced, and for this deployment, there is one rule for the port 80 listener and one rule for the 443 listener (whereby the port 80 rule redirects to the port 443 rule).

 

walterm_7-1634061167530.png

 

If the Helm shared Application Gateway option is turned on, there is a way to avoid modifying existing configurations for non-AKS applications using a Custom Resource Definition (CRD) of the kind AzureIngressProhibitedTarget (again, this is not an option with the AGIC add-on). This looks as follows in the Kubernetes manifest:

 

apiVersion: "appgw.ingress.k8s.io/v1"

kind: AzureIngressProhibitedTarget

metadata:

  name: prod-contoso-com

spec:

  hostname: prod.contoso.com

 

When the prohibited target manifest is deployed it must specify all hostnames to be ignored by AGIC. You can add as many hostnames as needed to ensure that AGIC does not bother any configurations associated with those hostnames. Instructions to set this up can be found here.  If there are only a few hostnames in an Application Gateway configured for AGIC, then this can be easily monitored to add the prohibited websites to the CRD, but if many non-AKS apps are to be deployed to the same Application Gateway it would be reasonable to have an Application Gateway with AGIC to serve only AKS deployments and another Application Gateway for non-AKS applications in order to avoid mistakenly overwriting a non-AKS application whose hostname was not entered into the prohibited target manifest (which would, of course, need to be redeployed with the updated prohibited targets).

 

Now, the next thing we want to do is deploy another Kubernetes application to demonstrate that you can now deploy Kubernetes applications to your hearts content, using the Azure voting application sample you can find here. Note that I modified the sample slightly by commenting out the type of the front end service so it would not use the standard Load Balancer:

 

apiVersion: apps/v1
kind: Deployment
metadata:
  name: azure-vote-back
spec:
  replicas: 1
  selector:
    matchLabels:
      app: azure-vote-back
  template:
    metadata:
      labels:
        app: azure-vote-back
    spec:
      nodeSelector:
        "beta.kubernetes.io/os": linux
      containers:
      - name: azure-vote-back
        image: mcr.microsoft.com/oss/bitnami/redis:6.0.8
        env:
        - name: ALLOW_EMPTY_PASSWORD
          value: "yes"
        ports:
        - containerPort: 6379
          name: redis
---
apiVersion: v1
kind: Service
metadata:
  name: azure-vote-back
spec:
  ports:
  - port: 6379
  selector:
    app: azure-vote-back
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: azure-vote-front
spec:
  replicas: 1
  selector:
    matchLabels:
      app: azure-vote-front
  strategy:
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
  minReadySeconds: 5
  template:
    metadata:
      labels:
        app: azure-vote-front
    spec:
      nodeSelector:
        "beta.kubernetes.io/os": linux
      containers:
      - name: azure-vote-front
        image: mcr.microsoft.com/azuredocs/azure-vote-front:v1
        ports:
        - containerPort: 80
        resources:
          requests:
            cpu: 250m
          limits:
            cpu: 500m
        env:
        - name: REDIS
          value: "azure-vote-back"
---
apiVersion: v1
kind: Service
metadata:
  name: azure-vote-front
spec:
  #type: LoadBalancer
  ports:
  - port: 80
  selector:
    app: azure-vote-front
 
I then back out the current Ingress object and redeploy with the following manifest (this assumes a wildcard certificate since it uses a subdomain, but it will still work):
 
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  annotations:
    kubernetes.io/ingress.class: azure/application-gateway
    #appgw.ingress.kubernetes.io/use-private-ip: "true"
    appgw.ingress.kubernetes.io/appgw-ssl-certificate: <your ssl certificate>
    appgw.ingress.kubernetes.io/ssl-redirect: "true"
spec:
  rules:
    - host: "<yourdomainname>"
      http:
        paths:
          - path: /
            backend:
              serviceName: aspnetapp
              servicePort: 80
    - host: "vote.<yourdomainname>"
      http:
        paths:
          - path: /
            backend:
              serviceName: azure-vote-front
              servicePort: 80
 
After the Ingress has been deployed, we have the following Backend pools:
 
walterm_0-1634177956202.png

 

Following are the Http settings:

 

 
walterm_0-1634178063919.png

 

Following are the listeners:

 

walterm_1-1634178093699.png

 

And finally, the updated Rules:

 

walterm_2-1634178122873.png

 

So that's a wrap on this article. I hope this helps you to better understand the behavior of AGIC, and I look forward to your feedback!

 
1 Comment
%3CLINGO-SUB%20id%3D%22lingo-sub-2839051%22%20slang%3D%22en-US%22%3EWhat%20Does%20It%20Mean%20for%20the%20Application%20Gateway%20Ingress%20Controller%20(AGIC)%20to%20Assume%20%E2%80%9CFull%20Ownership%E2%80%9D%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2839051%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20article%20pulls%20from%20two%20key%20Microsoft%20documentation%20sources%20on%20installation%20of%20Application%20Gateway%20Ingress%20Controller%20(AGIC)%20which%2C%20if%20read%20individually%2C%20can%20be%20a%20bit%20confusing%20if%20both%20aren%E2%80%99t%20factored%20together.%20The%20articles%20are%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapplication-gateway%2Fingress-controller-install-existing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EInstall%20an%20Application%20Gateway%20Ingress%20Controller%20(AGIC)%20using%20an%20existing%20Application%20Gateway%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapplication-gateway%2Ftutorial-ingress-controller-add-on-existing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETutorial%3A%20Enable%20Application%20Gateway%20Ingress%20Controller%20add-on%20for%20an%20existing%20AKS%20cluster%20with%20an%20existing%20Application%20Gateway%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EThe%20question%20we%20will%20tackle%20here%20is%20what%20does%20it%20mean%20in%20the%20documentation%20when%20we%20choose%20the%20%22Brownfield%22%20option%20for%20either%20Helm%20or%20the%20Ingress%20Controller%20Add-on%20where%20the%20documentation%20says%2C%20at%20least%20in%20the%20first%20article%2C%20that%20AGIC%20assumes%20%E2%80%9Cfull%20ownership%E2%80%9D%20of%20the%20Application%20Gateway%20it%20is%20associated%20with%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBasically%2C%20there%20are%20two%20ways%20to%20install%20AGIC%20on%20an%20existing%20Application%20Gateway%3A%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapplication-gateway%2Fingress-controller-install-existing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EHelm%3C%2FA%3E%20and%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapplication-gateway%2Ftutorial-ingress-controller-add-on-existing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAGIC%20add-on%20option%3C%2FA%3E.%20Only%20the%20Helm%20install%20supports%20the%20multi-cluster%2Fshared%20Application%20Gateway%20scenario%2C%20which%20must%20be%20explicitly%20specified%20as%20%E2%80%9Ctrue%E2%80%9D%20since%20%E2%80%9Cfalse%E2%80%9D%20is%20the%20default%20option.%20What%20this%20means%20is%20when%20shared%20is%20set%20to%20true%2C%20AGIC%20can%20support%20more%20than%20one%20AKS%20cluster%20and%20can%20also%20mix%20in%20other%20backends%20such%20as%20App%20Service%20or%20Virtual%20Machine%20Scale%20Sets.%20This%20may%20or%20may%20not%20be%20the%20best%20idea%20all%20depending.%20If%20the%20AGIC%20add-on%20option%20is%20used%2C%20currently%20there%20is%20no%20sharing%20the%20Application%20Gateway%20with%20other%20backends%2C%20and%20it%20does%20not%20support%20multiple%20AKS%20clusters%2C%20but%20the%20advantage%20is%20that%20it%20provides%20a%20fully%20managed%20experience%20and%20when%20AGIC%20is%20updated%20the%20add-on%20is%20automatically%20updated%20whereas%20with%20Helm%20any%20updates%20to%20AGIC%20must%20be%20performed%20manually.%20So%20if%20you%E2%80%99re%20going%20to%20install%20with%20Helm%20in%20the%20default%20mode%2C%20the%20AGIC%20add-on%20may%20be%20the%20better%20option%20as%20effectively%20it%20is%20the%20same%20thing%20but%20with%20the%20full%20managed%20experience.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Helm%20installation%20documentation%2C%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapplication-gateway%2Fingress-controller-install-existing%23multi-cluster--shared-application-gateway%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMulti-cluster%2FShared%20Gateway%3C%2FA%3E%20section%2C%20notes%20that%20with%20the%20%26nbsp%3Bdefault%20option%20(%3CEM%3Enot%3C%2FEM%3E%20shared)%2C%20AGIC%20will%20assume%20%E2%80%9Cfull%20ownership%E2%80%9D%20of%20the%20Application%20Gateway%20that%20AGIC%20is%20linked%20to%20(as%20does%20the%20AGIC%20add-on).%20What%20precisely%20does%20this%20mean%3F%20What%20it%20means%20is%20if%20you%20have%20an%20existing%20Application%20Gateway%20then%20any%20existing%20Backend%20pools%2C%20Http%20settings%2C%20Listeners%2C%20or%20Rules%2C%20when%20you%20deploy%20a%20workload%20to%20AKS%20with%20AGIC%20annotations%2C%20will%20either%20be%20deleted%20or%20rendered%20inoperative%20by%20default.%20And%20while%20the%20documentation%20presents%20a%20%E2%80%9Cbrownfield%E2%80%9D%20option%20for%20the%20AGIC%20add-on%2C%20it%20is%20actually%20%3CEM%3Enot%3C%2FEM%3E%20brownfield%20since%20it%20destroys%20whatever%20is%20already%20there%2C%20so%20do%20%3CEM%3Enot%3C%2FEM%3E%20use%20the%20AGIC%20add-on%20with%20an%20existing%20Application%20Gateway%20if%20you%20want%20to%20retain%20what%20configuration%20is%20already%20there.%20Below%20we%20will%20demonstrate%20what%20happens%20after%20AGIC%20is%20installed%20and%20subsequently%20an%20AKS%20application%20is%20deployed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBelow%20is%20a%20screenshot%20of%20two%20existing%20backend%20pools%20for%20two%20App%20Service%20applications%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_0-1634061006361.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316839i0A32876768D8432A%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_0-1634061006361.png%22%20alt%3D%22walterm_0-1634061006361.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBelow%20are%20the%20Http%20settings%20for%20each%20of%20the%20two%20applications%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_1-1634061042940.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316840i45CB4E590AAE9FB5%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_1-1634061042940.png%22%20alt%3D%22walterm_1-1634061042940.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20are%20two%20listeners%20for%20the%20app%20on%20port%2080%2C%20where%20the%20listener%20on%20port%2080%20performs%20a%20redirect%20to%20the%20listener%20on%20443%20(we%20will%20see%20this%20later%20with%20the%20AKS%20deployment).%20The%20second%20app%20uses%20https%20on%20port%208080.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_2-1634061062721.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316841i0DD9555C3B2AA630%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_2-1634061062721.png%22%20alt%3D%22walterm_2-1634061062721.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBelow%20are%20two%20rules%20for%20the%20first%20app%20tying%20the%20various%20listeners%20to%20their%20Http%20settings%20and%20backend%20pools%20(again%2C%20the%20%3CEM%3Edefaultrule%3C%2FEM%3E%20performs%20a%20redirect%20to%20the%20%3CEM%3Edefaulthttpsrule%3C%2FEM%3E).%20The%20other%20rule%20is%20for%20the%20second%20app.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_3-1634061080859.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316843i7BACCA5094307AE8%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_3-1634061080859.png%22%20alt%3D%22walterm_3-1634061080859.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20let%E2%80%99s%20take%20a%20look%20at%20the%20%3CA%20href%3D%22https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fapplication-gateway-kubernetes-ingress%2Fmaster%2Fdocs%2Fexamples%2Faspnetapp.yaml%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Esample%20Kubernetes%20manifest%3C%2FA%3E%20below%20that%20we%20will%20deploy%20leveraging%20AGIC%2C%20based%20on%20a%20common%20image%20in%20the%20Microsoft%20container%20registry.%20We%20have%20specified%20in%20annotations%20that%20we%20want%20to%20use%20AGIC%2C%20and%20we%20have%20specified%20our%20SSL%20certificate%20(which%20we%20added%20to%20Application%20Gateway%20previously%20using%20the%20%3CSTRONG%3Eaz%20network%20application-gateway%20ssl-cert%20create%3C%2FSTRONG%3E%20command)%2C%20and%20we%20have%20specified%20that%20we%20want%20SSL%20redirect%20(as%20discussed%20above).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EapiVersion%3A%20apps%2Fv1%3C%2FP%3E%0A%3CP%3Ekind%3A%20Deployment%3C%2FP%3E%0A%3CP%3Emetadata%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20name%3A%20aspnetapp-deployment%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20labels%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20app%3A%20aspnetapp%3C%2FP%3E%0A%3CP%3Espec%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20replicas%3A%203%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20selector%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20matchLabels%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20app%3A%20aspnetapp%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20template%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20metadata%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20labels%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20app%3A%20aspnetapp%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20spec%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20containers%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20-%20image%3A%20%22mcr.microsoft.com%2Fdotnet%2Fcore%2Fsamples%3Aaspnetapp%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20name%3A%20aspnetapp-image%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20ports%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20-%20containerPort%3A%2080%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20protocol%3A%20TCP%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E---%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EapiVersion%3A%20v1%3C%2FP%3E%0A%3CP%3Ekind%3A%20Service%3C%2FP%3E%0A%3CP%3Emetadata%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20name%3A%20aspnetapp%3C%2FP%3E%0A%3CP%3Espec%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20selector%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20app%3A%20aspnetapp%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20ports%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20-%20protocol%3A%20TCP%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20port%3A%2080%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20targetPort%3A%2080%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E---%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EapiVersion%3A%20extensions%2Fv1beta1%3C%2FP%3E%0A%3CP%3Ekind%3A%20Ingress%3C%2FP%3E%0A%3CP%3Emetadata%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20name%3A%20aspnetapp%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20annotations%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20kubernetes.io%2Fingress.class%3A%20azure%2Fapplication-gateway%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20appgw.ingress.kubernetes.io%2Fappgw-ssl-certificate%3A%20%3CEM%3E%3CNAME%20of%3D%22%22%20your%3D%22%22%20certificated%3D%22%22%20added%3D%22%22%20to%3D%22%22%20application%3D%22%22%20gateway%3D%22%22%3E%3C%2FNAME%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20appgw.ingress.kubernetes.io%2Fssl-redirect%3A%20%22true%22%3C%2FP%3E%0A%3CP%3Espec%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20rules%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20-%20http%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20paths%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20-%20path%3A%20%2F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20backend%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20serviceName%3A%20aspnetapp%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20servicePort%3A%2080%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnce%20deployed%2C%20we%20can%20now%20see%20how%20AGIC%20has%20effectively%20taken%20ownership%20of%20the%20Application%20Gateway.%20The%20%3CEM%3Edefaultaddresspool%3C%2FEM%3E%20was%20stripped%20of%20its%20rules%20and%20targets%2C%20and%20the%20%3CEM%3Esecondaddress%3C%2FEM%3E%20pool%20has%20been%20deleted.%20AGIC%20then%20adds%20its%20own%20backend%20pool%20for%20our%20AKS%20deployment.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_4-1634061110936.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316844i4DA43BD79B897624%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_4-1634061110936.png%22%20alt%3D%22walterm_4-1634061110936.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorwalterm_4%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3EIn%20Http%20settings%2C%20AGIC%20creates%20an%20entry%20for%20the%20AKS%20deployment%2C%20but%20leaves%20one%20of%20the%20existing%20Http%20settings%20and%20adds%20a%20probe%20to%20it%2C%20though%20it%20is%20not%20used%20for%20anything.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_5-1634061134310.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316846iB984799712E0DFD5%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_5-1634061134310.png%22%20alt%3D%22walterm_5-1634061134310.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorwalterm_5%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3ENow%20to%20the%20listeners.%20The%20existing%20listeners%20are%20all%20removed%2C%20and%20AGIC%20adds%20both%20a%20port%2080%20and%20443%20listener.%20As%20seen%20before%2C%20in%20the%20corresponding%20rules%20the%20port%2080%20listener%20will%20redirect%20to%20the%20443%20listener%2C%20which%20we%20specified%20in%20the%20above%20manifest%20with%20this%20annotation%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3Eappgw.ingress.kubernetes.io%2Fssl-redirect%3A%20%22true%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBelow%20is%20a%20screenshot%20of%20our%20listeners%20after%20the%20AKS%20deployment.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_6-1634061156196.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316847i5C950B8DF243C7DE%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_6-1634061156196.png%22%20alt%3D%22walterm_6-1634061156196.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorwalterm_6%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3EFinally%2C%20regarding%20rules%2C%20it%20is%20rules%20that%20tie%20the%20front%20end%20listener%20with%20the%20backend%20Http%20settings%20and%20Backend%20pools.%20The%20existing%20rules%20are%20completely%20replaced%2C%20and%20for%20this%20deployment%2C%20there%20is%20one%20rule%20for%20the%20port%2080%20listener%20and%20one%20rule%20for%20the%20443%20listener%20(whereby%20the%20port%2080%20rule%20redirects%20to%20the%20port%20443%20rule).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_7-1634061167530.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316848i9AE29E2D157135CC%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_7-1634061167530.png%22%20alt%3D%22walterm_7-1634061167530.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorwalterm_7%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3EIf%20the%20Helm%20shared%20Application%20Gateway%20option%20is%20turned%20on%2C%20there%20is%20a%20way%20to%20avoid%20modifying%20existing%20configurations%20for%20non-AKS%20applications%20using%20a%20Custom%20Resource%20Definition%20(CRD)%20of%20the%20kind%20%3CSTRONG%3EAzureIngressProhibitedTarget%20%3C%2FSTRONG%3E(again%2C%20this%20is%20%3CEM%3Enot%3C%2FEM%3E%20an%20option%20with%20the%20AGIC%20add-on).%20This%20looks%20as%20follows%20in%20the%20Kubernetes%20manifest%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EapiVersion%3A%20%22appgw.ingress.k8s.io%2Fv1%22%3C%2FP%3E%0A%3CP%3Ekind%3A%20AzureIngressProhibitedTarget%3C%2FP%3E%0A%3CP%3Emetadata%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20name%3A%20prod-contoso-com%3C%2FP%3E%0A%3CP%3Espec%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20hostname%3A%20prod.contoso.com%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20the%20prohibited%20target%20manifest%20is%20deployed%20it%20must%20specify%20all%20hostnames%20to%20be%20ignored%20by%20AGIC.%20You%20can%20add%20as%20many%20hostnames%20as%20needed%20to%20ensure%20that%20AGIC%20does%20not%20bother%20any%20configurations%20associated%20with%20those%20hostnames.%20Instructions%20to%20set%20this%20up%20can%20be%20found%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fapplication-gateway%2Fingress-controller-install-existing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%26nbsp%3B%20If%20there%20are%20only%20a%20few%20hostnames%20in%20an%20Application%20Gateway%20configured%20for%20AGIC%2C%20then%20this%20can%20be%20easily%20monitored%20to%20add%20the%20prohibited%20websites%20to%20the%20CRD%2C%20but%20if%20many%20non-AKS%20apps%20are%20to%20be%20deployed%20to%20the%20same%20Application%20Gateway%20it%20would%20be%20reasonable%20to%20have%20an%20Application%20Gateway%20with%20AGIC%20to%20serve%20only%20AKS%20deployments%20and%20%3CEM%3Eanother%3C%2FEM%3E%20Application%20Gateway%20for%20non-AKS%20applications%20in%20order%20to%20avoid%20mistakenly%20overwriting%20a%20non-AKS%20application%20whose%20hostname%20was%20not%20entered%20into%20the%20prohibited%20target%20manifest%20(which%20would%2C%20of%20course%2C%20need%20to%20be%20redeployed%20with%20the%20updated%20prohibited%20targets).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%2C%20the%20next%20thing%20we%20want%20to%20do%20is%20deploy%20another%20Kubernetes%20application%20to%20demonstrate%20that%20you%20can%20now%20deploy%20Kubernetes%20applications%20to%20your%20hearts%20content%2C%20using%20the%20Azure%20voting%20application%20sample%20you%20can%20find%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Faks%2Fkubernetes-walkthrough%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20Note%20that%20I%20modified%20the%20sample%20slightly%20by%20commenting%20out%20the%20type%20of%20the%20front%20end%20service%20so%20it%20would%20not%20use%20the%20standard%20Load%20Balancer%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%3E%0A%3CDIV%3E%3CSPAN%3EapiVersion%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eapps%2Fv1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Ekind%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3EDeployment%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Emetadata%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-back%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Espec%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ereplicas%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eselector%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EmatchLabels%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eapp%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-back%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Etemplate%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Emetadata%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Elabels%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eapp%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-back%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Espec%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EnodeSelector%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3E%22beta.kubernetes.io%2Fos%22%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Elinux%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Econtainers%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-back%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eimage%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Emcr.microsoft.com%2Foss%2Fbitnami%2Fredis%3A6.0.8%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eenv%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3EALLOW_EMPTY_PASSWORD%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Evalue%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E%22yes%22%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eports%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3EcontainerPort%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E6379%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eredis%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E---%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3EapiVersion%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Ev1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Ekind%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3EService%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Emetadata%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-back%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Espec%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eports%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Eport%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E6379%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eselector%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eapp%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-back%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E---%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3EapiVersion%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eapps%2Fv1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Ekind%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3EDeployment%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Emetadata%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-front%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Espec%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ereplicas%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eselector%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EmatchLabels%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eapp%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-front%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Estrategy%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3ErollingUpdate%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EmaxSurge%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EmaxUnavailable%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EminReadySeconds%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E5%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Etemplate%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Emetadata%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Elabels%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eapp%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-front%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Espec%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EnodeSelector%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3E%22beta.kubernetes.io%2Fos%22%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Elinux%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Econtainers%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-front%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eimage%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Emcr.microsoft.com%2Fazuredocs%2Fazure-vote-front%3Av1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eports%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3EcontainerPort%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E80%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eresources%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Erequests%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ecpu%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E250m%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Elimits%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ecpu%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E500m%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eenv%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3EREDIS%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Evalue%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E%22azure-vote-back%22%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E---%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3EapiVersion%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Ev1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Ekind%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3EService%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Emetadata%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-front%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Espec%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3E%23type%3A%20LoadBalancer%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eports%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Eport%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E80%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eselector%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eapp%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-front%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3EI%20then%20back%20out%20the%20current%20Ingress%20object%20and%20redeploy%20with%20the%20following%20manifest%20(this%20assumes%20a%20wildcard%20certificate%20since%20it%20uses%20a%20subdomain%2C%20but%20it%20will%20still%20work)%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3E%3CSPAN%3EapiVersion%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eextensions%2Fv1beta1%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Ekind%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3EIngress%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Emetadata%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ename%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Etest-ingress%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eannotations%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ekubernetes.io%2Fingress.class%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure%2Fapplication-gateway%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3E%23appgw.ingress.kubernetes.io%2Fuse-private-ip%3A%20%22true%22%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eappgw.ingress.kubernetes.io%2Fappgw-ssl-certificate%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CEM%3E%3CYOUR%20ssl%3D%22%22%20certificate%3D%22%22%3E%3C%2FYOUR%3E%3C%2FEM%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Eappgw.ingress.kubernetes.io%2Fssl-redirect%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E%22true%22%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3Espec%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Erules%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Ehost%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E%22%3CEM%3E%3CYOURDOMAINNAME%3E%3C%2FYOURDOMAINNAME%3E%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ehttp%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Epaths%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Epath%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E%2F%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ebackend%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EserviceName%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Easpnetapp%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EservicePort%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E80%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Ehost%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E%22vote.%3CEM%3E%3CYOURDOMAINNAME%3E%3C%2FYOURDOMAINNAME%3E%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ehttp%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Epaths%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20-%20%3C%2FSPAN%3E%3CSPAN%3Epath%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E%2F%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3Ebackend%3C%2FSPAN%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EserviceName%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3Eazure-vote-front%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EservicePort%3C%2FSPAN%3E%3CSPAN%3E%3A%20%3C%2FSPAN%3E%3CSPAN%3E80%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3EAfter%20the%20Ingress%20has%20been%20deployed%2C%20we%20have%20the%20following%20Backend%20pools%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_0-1634177956202.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317240iACCEE6E89131127A%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_0-1634177956202.png%22%20alt%3D%22walterm_0-1634177956202.png%22%20%2F%3E%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFollowing%20are%20the%20Http%20settings%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorwalterm_3%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_0-1634178063919.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317244i6607A7AB57A113B9%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_0-1634178063919.png%22%20alt%3D%22walterm_0-1634178063919.png%22%20%2F%3E%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFollowing%20are%20the%20listeners%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_1-1634178093699.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317245iD1C17D9B72D6AB1B%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_1-1634178093699.png%22%20alt%3D%22walterm_1-1634178093699.png%22%20%2F%3E%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20finally%2C%20the%20updated%20Rules%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22walterm_2-1634178122873.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317246iDF388155D3374368%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22walterm_2-1634178122873.png%22%20alt%3D%22walterm_2-1634178122873.png%22%20%2F%3E%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20that's%20a%20wrap%20on%20this%20article.%20I%20hope%20this%20helps%20you%20to%20better%20understand%20the%20behavior%20of%20AGIC%2C%20and%20I%20look%20forward%20to%20your%20feedback!%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2839051%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20does%20it%20mean%20in%20the%20Application%20Gateway%20documentation%20when%20it%20notes%20that%20the%20Application%20Gateway%20Ingress%20Controller%20(AGIC)%20for%20Azure%20Kubernetes%20Service%20(AKS)%20assumes%20%E2%80%9Cfull%20ownership%E2%80%9D%20of%20the%20Application%20Gateway%20it%20is%20associated%20with%3F%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2839051%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApp%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECloud%20Native%20Apps%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2957326%22%20slang%3D%22en-US%22%3ERe%3A%20What%20Does%20It%20Mean%20for%20the%20Application%20Gateway%20Ingress%20Controller%20(AGIC)%20to%20Assume%20%E2%80%9CFull%20Ownershi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2957326%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20write-up%20and%20very%20helpful%20as%20the%20documentation%20is%20lacking%20here.%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Oct 19 2021 01:43 PM
Updated by: