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

Add "major" and "major.minor" version tags on docker images #1594

Open
nop-infra opened this issue Oct 23, 2023 · 2 comments
Open

Add "major" and "major.minor" version tags on docker images #1594

nop-infra opened this issue Oct 23, 2023 · 2 comments
Assignees
Labels
enhancement needs triage Waiting for discussion / prioritization by team
Milestone

Comments

@nop-infra
Copy link

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I am using the step-ca docker image in production.
I do not want to use the "latest" tag, to prevent updating the containers to a major version (with breaking changes) by accident.
Today, I have to tag the exact version (major.minor.patch) and manually updating it each time there is a new version.

It would be great to have "major" and "major.minor" tags on docker hub to make maintenance more convenient.

Today, version tags on docker hub only uses full version of semantic versioning : major.minor.patch (0.25.0 for example)

It would be great to have the following tags :

  • "major" (0 for example) : this is the latest image version for the major version 0
  • "major.minor" (0.25 for example) : this is the latest version the the minor version 0.25

Why is this needed?

With these two new tag type, it becomes possible to :

  • If using "major" tag : fix the major version and ensure it is up to date, with all minor update and patches. The update is automatic as with "latest" but we ensure the container is not updated to another major version
  • If using "major.minor" tag : fix the minor version and ensure it is up to date, with all the patches applied.
@nop-infra nop-infra added enhancement needs triage Waiting for discussion / prioritization by team labels Oct 23, 2023
@4x0v7
Copy link

4x0v7 commented Oct 24, 2023

Hey there!
While I agree this would be useful, in production prefer to pin the version, to ensure the exact image is used.
For example smallstep/step-ca:0.25.0@sha256:9cdef9c9daecf71d87d23d83a57712867e6c08d4f9ecad998d4bc6239f2218dd

@nop-infra
Copy link
Author

Hi !

Thank you for your reply.
I understand this could be the recommended approach, but why would you prefer this to pining 0.25 tag for example ?

In my case, as described in the issue, this would be very useful. A lot of organizations that ship official docker images use this approach, it would be great if step-ca could provide that to.

Do you plan on adding the tags the near future ? If I can contribute in any way to speed up the process, feel free to poke me !

@hslatman hslatman added this to the v0.25.1 milestone Oct 24, 2023
@hslatman hslatman modified the milestones: v0.25.1, v0.25.2 Nov 29, 2023
@hslatman hslatman modified the milestones: v0.26.0, v0.26.1 Mar 29, 2024
@hslatman hslatman modified the milestones: v0.26.1, v0.26.2 Apr 25, 2024
@hslatman hslatman modified the milestones: v0.26.2, v0.26.3 Jun 17, 2024
@hslatman hslatman modified the milestones: v0.27.0, v0.27.2 Jul 15, 2024
@hslatman hslatman modified the milestones: v0.27.2, v0.27.3 Jul 23, 2024
@hslatman hslatman modified the milestones: v0.27.3, v0.27.5 Sep 16, 2024
@hslatman hslatman modified the milestones: v0.27.5, v0.27.6 Oct 22, 2024
@hslatman hslatman modified the milestones: v0.28.0, v0.28.1 Oct 30, 2024
@hslatman hslatman modified the milestones: v0.28.1, v0.28.2 Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

4 participants