Answers: <p>just create an ingress resource along side each application, that way you can modify individual ingress resources without impacting other applications. Load balancers do not allow you to do anything meaningful with your traffic.</p>
  
  <p>With ingress you can use cert-manager, external-dns, ssl offloading, etc.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-03-03T10:29:46.730Z
Answers: 2019-03-03T10:29:46.730Z
Answers: 4c74356b41
Answers: <p>I generally use an Ingress for each application. This allows for any updates to it to be specified as a separate deployable unit. If there is a need for separate public IPs, you can have multiple ingress controllers for different namespaces/environments.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-03-01T20:05:05.007Z
Answers: 2019-03-01T20:05:05.007Z
Answers: Marcus
Body: <p>I'm wondering whether to use an Ingress or LoadBalancer to expose services on Azure AKS.</p>
  
  <p>I have successfully used both, but I cannot really choose. On one side, an Ingress allows us to have a single public IP address, but on the other end it factorizes all the routes inside one Ingress so deployment means impacting all the routes.</p>
  
  <p>Would you recommend:</p>
  
  <ul>
  <li>a common Ingress for all applications</li>
  <li>an Ingress for each application;</li>
  <li>a LoadBalancer for each service ?</li>
  </ul>
  
Tags: <kubernetes><azure><azure-kubernetes-service>
Title: Ingress or LoadBalancer on AKS
UserDisplayName: Arnaud Weil
ThreadText: # Ingress or LoadBalancer on AKS
  
  (Asked by: username_0 on 2019-02-28)
  
  I'm wondering whether to use an Ingress or LoadBalancer to expose services on Azure AKS.
  
  I have successfully used both, but I cannot really choose. On one side, an Ingress allows us to have a single public IP address, but on the other end it factorizes all the routes inside one Ingress so deployment means impacting all the routes.
  
  Would you recommend:
  
  * a common Ingress for all applications
  * an Ingress for each application;
  * a LoadBalancer for each service ?
  
  **Tags:** kubernetes, azure, azure-kubernetes-service
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-03-03. Score: 2 | Accepted answer
  
  just create an ingress resource along side each application, that way you can modify individual ingress resources without impacting other applications. Load balancers do not allow you to do anything meaningful with your traffic.
  
  With ingress you can use cert-manager, external-dns, ssl offloading, etc.
  
  
  ---
  
  ### Answer by username_2 on 2019-03-01. Score: 1
  
  I generally use an Ingress for each application. This allows for any updates to it to be specified as a separate deployable unit. If there is a need for separate public IPs, you can have multiple ingress controllers for different namespaces/environments.
  
  
  ---
  
  