-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting different service tags for different ports in AKS/Helm? #5341
Comments
/kind support |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Public AKS documentation indicates that the annotation service.beta.kubernetes.io/azure-allowed-service-tags can be used in a Helm service yaml of type LoadBalancer to configure service tags on the Network Security Group inbound rules associated with the public endpoint of an AKS cluster. This works.
However, I couldn't find a way to configure the service tags to apply to one specific port opened by the load balancer, and not to others. When creating NSG rules by hand in the Azure Portal, the rule requires inbound service tag, destination IP and destination port. No such distinction is available via the Helm annotations.
How can a service tag be configured via helm on a specific port? Is there a workaround? If this is not supported, can it be added?
The text was updated successfully, but these errors were encountered: