-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Docs: add note about AKS kube-apiserver entity #32464
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgmt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
Is there an easy way to check whether the entity is available for a specific distribution?
No that I'm aware of. I will do some tests on EKS and GKE next week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you clarify what you mean by "unavailable"? As far as I understand it, kube-apiserver
works fine for egress traffic, even on AKS. But it won't work for ingress traffic (because of NAT) (ref #31711 (comment))
You're absolutely right; the note should mention that only ingress statements with |
231ab10
to
a662363
Compare
I tested against AKS, EKS and GKE and the behaviour is the same. |
Adds a note to the docs that `kube-apiserver` entity is not available for ingress traffic in AKS, EKS and GKE. Signed-off-by: darox <maderdario@gmail.com>
a662363
to
26d4be4
Compare
/test |
Adds a note to the docs that
kube-apiserver
entity is not available in AKS.