Skip to content
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

Open
MattPOlson opened this issue Jul 6, 2022 · 9 comments
Open

Configure Nodes to Access Secure Registries #1124

MattPOlson opened this issue Jul 6, 2022 · 9 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@MattPOlson
Copy link

MattPOlson commented Jul 6, 2022

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.

      config_path = ""

      [plugins."io.containerd.grpc.v1.cri".registry.auths]

      [plugins."io.containerd.grpc.v1.cri".registry.configs]
        [plugins."io.containerd.grpc.v1.cri".registry.configs."my-registry.com".auth]
          auth = "*************"

      [plugins."io.containerd.grpc.v1.cri".registry.headers] 



@jrvaldes
Copy link
Contributor

@MattPOlson, WINC-846 was created to track this work.

@jrvaldes
Copy link
Contributor

/close

@openshift-ci openshift-ci bot closed this as completed Jul 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 19, 2022

@jrvaldes: Closing this issue.

In response to this:

/close

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.

@sebsoto
Copy link
Contributor

sebsoto commented Aug 3, 2022

/reopen

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 3, 2022

@sebsoto: Reopened this issue.

In response to this:

/reopen

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.

@openshift-ci openshift-ci bot reopened this Aug 3, 2022
@sebsoto
Copy link
Contributor

sebsoto commented Aug 3, 2022

Keeping this open so its tracked on Github as well

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2022
@sebsoto
Copy link
Contributor

sebsoto commented Nov 2, 2022

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2022
@sebsoto
Copy link
Contributor

sebsoto commented Nov 2, 2022

/lifecycle frozen

@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants