-
Notifications
You must be signed in to change notification settings - Fork 68
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
Configure Nodes to Access Secure Registries #1124
Comments
@MattPOlson, WINC-846 was created to track this work. |
/close |
@jrvaldes: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@sebsoto: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Keeping this open so its tracked on Github as well |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/lifecycle frozen |
This is a feature request for the following. With the current version of the operator that uses containerd the toml file at C:\k\containerd on each of the nodes needs to be modified to allow auth to the private registry. Currently every time a windows node is provisioned there is a manual step to allow it to pull from the registry. If the operator could read from the same secret that the coreos nodes use and configure the toml file on the nodes this would eliminate the manual step currently needed. Below is an example of the config file to allow access.
The text was updated successfully, but these errors were encountered: