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.

Sign up for GitHub

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

Jump to bottom

skydns depends on quay.io/coreos/etcd:latest #4743

Closed
alex-mohr opened this issue Feb 23, 2015 · 3 comments
Closed

skydns depends on quay.io/coreos/etcd:latest #4743

alex-mohr opened this issue Feb 23, 2015 · 3 comments
Labels
area/reliability priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.0

Comments

@alex-mohr
Copy link
Contributor

The DNS addon has a dependency on a container image "quay.io/coreos/etcd:latest". That's currently v0.4.6, but will presumably shift to v2.x at some point.

To prevent an incident when that happens, we should launch etcd from a known-good version that's known-compatible with skydns -- not :latest.
@alex-mohr alex-mohr added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/reliability team/cluster labels Feb 23, 2015
@alex-mohr alex-mohr added this to the v1.0 milestone Feb 23, 2015
@rsokolowski rsokolowski self-assigned this Feb 24, 2015
@rsokolowski
Copy link
Contributor

The easiest thing is to replace latest with v0.4.6, however this version has issues like https://github.com/coreos/etcdctl/issues/109
I've checked with v2.0.0 and DNS works however I've encountered etcd-io/etcd#2253.
Since API-server's etcd is being converted to v2.0.3 ( #4442) I'm going to use the same version and just fix the command line to make etcd accessible from outside (etcdctl).

@dchen1107
Copy link
Member

coreos folks patched etcd 2.0, and built v2.0.3 for us: https://quay.io/repository/coreos/etcd?tag=v2.0.3

@zmerlynn zmerlynn mentioned this issue Feb 25, 2015
Merged
@brendandburns
Copy link
Contributor

Closing this as we are now locked to 2.0.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/reliability priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
4 participants
@brendandburns @dchen1107 @alex-mohr @rsokolowski