-
Notifications
You must be signed in to change notification settings - Fork 312
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
Instance Metadata endpoint Restriction #2823
Comments
Action required from @Azure/aks-pm |
Action required from @Azure/aks-pm |
Action required from @Azure/aks-pm |
Action required from @Azure/aks-pm |
Issue needing attention of @Azure/aks-leads |
Action required from @Azure/aks-pm |
The documented instructions for IMDS hardening were proven problematic to achieve by manual means (on Azure CNI at least), as azure-npm doesn't cope well with introducing a large number of NetworkPolicy objects at once. I wish there was a recommended way of achieving this, especially for someone using Azure CNI. |
Action required from @Azure/aks-pm |
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. miwithro 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. |
@miwithrow, @CocoWang-wql would you be able to assist? |
Closing as duplicate of #4037 |
Enable a Feature to allow customers to prevent unprivileged pods from accessing HostNetwork which provides access to the IMDS endpoint.
The text was updated successfully, but these errors were encountered: