You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using NAP in AKS, I would like to be able to enable public IP for the nodes, as well as the Node Public IP Prefix to be used. I need to expose workloads directly through the hostPort and have those host be exposed to the public internet for performance reasons.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently, this is feasible through regular NodePools, but the hard limitation of 100 node pools in a given cluster is limiting for our use case. I'm investigating if NAP would work for us, but this feature missing is a potential blocker.
Are you currently working around this issue?
We are currently in the process of figuring out how we will solve those issues.
Additional Context
No response
Attachments
No response
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Tell us about your request
Using NAP in AKS, I would like to be able to enable public IP for the nodes, as well as the Node Public IP Prefix to be used. I need to expose workloads directly through the
hostPort
and have those host be exposed to the public internet for performance reasons.Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently, this is feasible through regular NodePools, but the hard limitation of 100 node pools in a given cluster is limiting for our use case. I'm investigating if NAP would work for us, but this feature missing is a potential blocker.
Are you currently working around this issue?
We are currently in the process of figuring out how we will solve those issues.
Additional Context
No response
Attachments
No response
Community Note
The text was updated successfully, but these errors were encountered: