-
Notifications
You must be signed in to change notification settings - Fork 200
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
Docker Tag Names #33
Comments
Yes, sorry about this - it's essentially an artefact of the fact that we continuously deploy kured internally, so there's no pressure on me to make external releases. The original plan was to tag an official release every time a new minor version of kubernetes came out, and publish the corresponding manifest on the release page, but as you can see I didn't keep up with that commitment. I'm about to do a formal release based on 1.12.x kubectl/client-go - watch this space. Probably the right thing for me to do is to change our internal process so that master builds are deployed continuously to our development environment, but only deploy semver tagged builds to production to give myself motivation 😄 |
I just realized another great option besides tags for Docker images would be a compatibility matrix matching kured to the kubernetes releases. Tags would stay the same and information would still be easy to access. Looking forward to a new release 👍 |
The Docker image tags available at https://quay.io/repository/weaveworks/kured?tab=tags are challenging. Based on the tag name or information given I can hardly identify what version is running. Especially difficult considering upgrading a Kubernetes cluster to a new version. In this case I would like to update kured to a newer version as well; preferably to the respective kubectl version. Docker tags would help to identify the right version of kured to deploy.
The text was updated successfully, but these errors were encountered: