-
Notifications
You must be signed in to change notification settings - Fork 453
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
Explicitly list the container registry by default #328
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Pat Riehecky <[email protected]>
This would introduce a breaking change for everyone currently configuring a registry as part of
resulting in (broken):
We could use a backwards-compatible approach, like the rancher-system charts:
However, this still requires you to provide custom values with the registry. I don't see a backwards-compatible way that would allow us to configure |
That possibility non-defaulting to I could switch the default registry to |
@jcpunk The break change is a concern. Need to figure out a solution to it. |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
I'll confess some interest in this still |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
I'll confess some interest in this still |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
I'll confess some interest in this still, any thoughts on how to proceed? |
@jcpunk let's put it in the next release. Thanks. |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
I'd still like to see some version of this. |
For my auditors, they want the registry listed for each container we are running. Storing it here makes generating my reports much easier.