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

Explicitly list the container registry by default #328

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jcpunk
Copy link

@jcpunk jcpunk commented Apr 18, 2023

For my auditors, they want the registry listed for each container we are running. Storing it here makes generating my reports much easier.

@anothertobi
Copy link
Contributor

This would introduce a breaking change for everyone currently configuring a registry as part of .image.repository like:

image:
  repository: registry.mycompany.com/rancher/local-path-provisioner

resulting in (broken):

image: "docker.io/registry.mycompany.com/rancher/local-path-provisioner:master-head"

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 docker.io as the default registry in the Helm chart (non-empty default registry) since there are also some edge-cases where systems don't default to docker.io when no registry is given.

@jcpunk
Copy link
Author

jcpunk commented Apr 24, 2023

That possibility non-defaulting to docker.io is what has our audit team concerned. Without an explicit origin path they are uncomfortable. I figured that discomfort might be shared by others and was hopeful for some sort of way clean up my site and provide something beneficial.

I could switch the default registry to None and wrap it in logic so we don't get a weird leading / and keep docker.io in my local values.yaml but still track the image and tag from the chart. Having the chart default to explicit would be my ideal, but sometimes life is like that.

@derekbit
Copy link
Member

@jcpunk The break change is a concern. Need to figure out a solution to it.

Copy link

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.

@github-actions github-actions bot added the stale label Jun 11, 2024
@jcpunk
Copy link
Author

jcpunk commented Jun 11, 2024

I'll confess some interest in this still

@github-actions github-actions bot removed the stale label Jun 12, 2024
Copy link

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.

@github-actions github-actions bot added the stale label Jul 28, 2024
@jcpunk
Copy link
Author

jcpunk commented Jul 28, 2024

I'll confess some interest in this still

@github-actions github-actions bot removed the stale label Jul 29, 2024
Copy link

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.

@github-actions github-actions bot added the stale label Sep 12, 2024
@jcpunk
Copy link
Author

jcpunk commented Sep 12, 2024

I'll confess some interest in this still, any thoughts on how to proceed?

@derekbit
Copy link
Member

@jcpunk let's put it in the next release. Thanks.

@github-actions github-actions bot removed the stale label Sep 13, 2024
Copy link

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.

@github-actions github-actions bot added the stale label Oct 28, 2024
@jcpunk
Copy link
Author

jcpunk commented Oct 28, 2024

I'd still like to see some version of this.

@github-actions github-actions bot removed the stale label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants