-
Notifications
You must be signed in to change notification settings - Fork 302
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
AKS Containerd localhost behavior different than upstream? #3303
Comments
Action required from @Azure/aks-pm |
Issue needing attention of @Azure/aks-leads |
2 similar comments
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Also may be a security concern: GHSA-2qjp-425j-52j9. |
Issue needing attention of @Azure/aks-leads |
11 similar comments
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
Issue needing attention of @Azure/aks-leads |
This issue will now be closed because it hasn't had any activity for 7 days after stale. jeff-mccoy feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion. |
Zarf uses a NodePort bound to
127.0.0.1
to connect to a local registry. On all other containerd-based clusters this allows us to point to127.0.0.1
and containerd will usehttp
instead ofhttps
. It seems there is something different happening on the azure version of containerd, even runningcrictl pull
in a debug node on AKS demonstrates this behavior. Previously, this was not on an issue on AKS, but that was early this year. Is there something special that the Azure version of containerd is doing with localhost that differs from the upstream? Also is there a way to change this behavior or specify an insecure registry for localhost?Related issues for zarf:
The text was updated successfully, but these errors were encountered: