This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 255
[Azure Firewall + add-pod-identity] watching problem #467
Labels
bug
Something isn't working
Comments
ferantivero
changed the title
[Azure Firewall + add-pod-identity] watch problem
[Azure Firewall + add-pod-identity] watching problem
Jan 3, 2020
We experience the exact same thing. Looking for a production solution. |
Both egress lockdown as well as aad pod identity are key for enterprise scenarios. They should also work together. /Cc @ritazh |
Thank you for opening the issue. We will investigate this and update the issue. |
Hi @aramase thanks. If you need additional information on the issue, please let us know. |
@sbkg0002 @ferantivero I was able to recreate the issue. There are 2 options to mitigate this -
This should resolve the issue. Let me know if this helps. I'll update the docs soon. |
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Symptom
when restricting egress traffic in an aks cluster using Azure Firewall, aad pod identity starts failing while trying to watch.
Azure Firewall logs
the following is the only denied HTTPS request:
from user's voice: https://feedback.azure.com/forums/217313-networking/suggestions/38623357-disable-sni-tls-extension-check-on-azure-firewall
nmi pod
kubectl get po nmi-szsqt -o wide
kubernetes svc
kubectl get svc kubernetes
nmi logs
Workarounds
Although it isn't valid in our configuration scenario (production), please let us share a temporary workaround:
Steps To Reproduce
rt.services.visualstudio.com:443
allowing as source your aks cluster subnet cidr onlyExpected behavior
no errors should be displayed from logs
AAD Pod Identity version
mcr.microsoft.com/k8s/aad-pod-identity/nmi:1.5.4
mcr.microsoft.com/k8s/aad-pod-identity/mic:1.5.4
Kubernetes version
client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"2640ac46d96791a135961425127d9c2f7e184924", GitTreeState:"clean", BuildDate:"2019-11-14T04:58:54Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Additional context
EDIT: found this upstream in case it helps kubernetes/client-go#173
EDIT1: just a bit more context on the Azure Firewall SNI
Deny
log entry, since I'm not adding the ASK Api Server Public Ip from my Network Rules (no rules match found), it proceeds to Application Rules, and under that set collection of rules (FQDN), SNI extension could be required.The text was updated successfully, but these errors were encountered: