Skip to content
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

Load balancing doesn't work correctly in BYO VNET scenarios #562

Open
ohorvath opened this issue Nov 4, 2024 · 1 comment
Open

Load balancing doesn't work correctly in BYO VNET scenarios #562

ohorvath opened this issue Nov 4, 2024 · 1 comment
Assignees
Labels
area/networking Issues or PRs related to networking triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ohorvath
Copy link

ohorvath commented Nov 4, 2024

Version

Karpenter Version: v0.7.0

Kubernetes Version: v1.3.0

If you use BYO VNET for your AKS cluster with Standard Public LB, the ingress traffic only hits the nodes of the system nodepool and not the karpenter nodes. In this scenario AKS automatically creates a NSG and attaches it to the network interfaces of the system nodes and not to the karpenter nodes. This behavior ultimately blocks the ingress traffic to reach karpenter nodes. If the externalTrafficPolicy is set to Cluster, the traffic can reach the nodes through an extra hop from the system nodes but never directly. However if you set the externalTrafficPolicy to Local, there is no way to forward ingress traffic to the karpenter nodes.

Expected Behavior

An NSG should be associated with the karpenter nodes also, not just with the system nodes to enable ingress traffic from the public LB.

Actual Behavior

See above, due to the missing NSG, traffic can't reach the karpenter nodes directly.

Steps to Reproduce the Problem

Create a cluster with karpenter.
Install NGINX ingress controller with externalTrafficPolicy set to local.
Force the NGINX pods to move to the karpenter nodes.
Create an ingress and a backend app.
Try to reach the public LB externally.

Resource Specs and Logs

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
@tallaxes tallaxes added triage/accepted Indicates an issue or PR is ready to be actively worked on. area/networking Issues or PRs related to networking labels Dec 4, 2024
@tallaxes tallaxes self-assigned this Dec 4, 2024
@johnthompson-ybor
Copy link

I have the same problem, i opened a separate issue for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking Issues or PRs related to networking triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants