aks-app-routing-operator
aks-app-routing-operator copied to clipboard
Azure
Remove default nginx ingress controller
Hi,
Is it possible to remove the default nginx ingress controller?. At my current employer, we do not need to deploy the default public ingress controller, instead we just need only an internal one. With the current implementation of aks-app-routing-operator (source), the default controller always gets created which always creates a public load balancer.
I have seen https://github.com/Azure/aks-app-routing-operator/pull/189, but not sure how to use it.
BTW, even w/o that PR, you still can replace the default one like here: https://github.com/Azure/AKS/issues/4233#issuecomment-2076336636
Hi,
Is it possible to remove the default nginx ingress controller?. At my current employer, we do not need to deploy the default public ingress controller, instead we just need only an internal one. With the current implementation of aks-app-routing-operator (source), the
defaultcontroller always gets created which always creates a public load balancer.
This will be a new feature in the next month or two as part of the AKS ARM configuration. You'll be able to specify if you want a public, internal, or no default Ingress Controller.
In the meantime, I recommend the suggestion above of editing the default one.
@JoeyC-Dev thank you for the insight. I just wanted to avoid patching a resource that we do not control directly (the default controller). On the other hand, what @OliverMKing mentioned sounds even better. Looking forward for the update :)
@OliverMKing Would the new feature include the ability to create a connected Private Link Service as per this doc or would we still need to patch the default resource?
https://learn.microsoft.com/en-us/azure/aks/internal-lb?tabs=set-service-annotations#create-a-private-link-service-connection
@OliverMKing Would the new feature include the ability to create a connected Private Link Service as per this doc or would we still need to patch the default resource?
https://learn.microsoft.com/en-us/azure/aks/internal-lb?tabs=set-service-annotations#create-a-private-link-service-connection
The feature would allow you to specify "no default" and go completely custom. In that case, you'd fully control the lifecycle of all NginxIngressController custom resources and could connect with Private Link Service that way.
This is now possible: https://learn.microsoft.com/en-us/azure/aks/app-routing-nginx-configuration?tabs=bicep#control-the-default-nginx-ingress-controller-configuration
Looks like the az-cli support is coming soon: https://github.com/Azure/azure-cli-extensions/pull/7865
See https://github.com/hashicorp/terraform-provider-azurerm/issues/27109 for the azurerm provider. Since it is still in preview they will wait for it to go to GA.
