Skip to content

Federation API server is failing to process requests. #39594

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
madhusudancs opened this issue Jan 9, 2017 · 5 comments · Fixed by #39646
Closed

Federation API server is failing to process requests. #39594

madhusudancs opened this issue Jan 9, 2017 · 5 comments · Fixed by #39646
Assignees
@nikhiljindal
Labels
area/etcd
Milestone
v1.6

Comments

@madhusudancs
Copy link
Contributor

It looks like an etcd3 compatibility issue from the initial debugging, but I haven't had a chance to do a thorough analysis.

Federation control plane creates an etcd container with an etcd2 image and recent changes announced here https://groups.google.com/forum/#!topic/kubernetes-dev/WMPK5fyOorE might be the reason for the failures.

Were there any changes to generic API server to make this change happen?

@nikhiljindal @shashidharatd, could one of you please take a look?

cc @kubernetes/sig-federation-misc @nikhiljindal @shashidharatd @csbell @timothysc
@madhusudancs madhusudancs added this to the v1.6 milestone Jan 9, 2017
@shashidharatd
Copy link

Yes @madhusudancs, the upgrade in etcd is causing the issues.
we need to upgrade etcd image to gcr.io/google_containers/etcd:3.0.14-alpha.1 for federation

@nikhiljindal
Copy link
Contributor

Why alpha image?
Dont we have a stable etcd:3.0 image?

@shashidharatd
Copy link

This is the image used in base kubernetes for etcd. Not sure why it is alpha

@madhusudancs
Copy link
Contributor Author

madhusudancs commented Jan 9, 2017 •
edited
Loading

@nikhiljindal

Why alpha image?
Dont we have a stable etcd:3.0 image?

This is the image we use in Kubernetes clusters. I believe this image's release cycle is tied to Kubernetes release cycle, which is also in alpha.

Also note, etcd 3.0.14 is stable. I believe this is our modified version of the image that ships with necessary migration bits.

@kubernetes/sig-scalability-misc, is this correct?

@timothysc
Copy link
Member

it's not alpha, that was just a tag applied by folks adding the image to gcrio.

Yes 3.0.14 is the correct version.

@shashidharatd shashidharatd mentioned this issue Jan 10, 2017
Merged
k8s-github-robot pushed a commit that referenced this issue Jan 11, 2017
Merge pull request #39646 from shashidharatd/federation-misc
3888aca 
Automatic merge from submit-queue (batch tested with PRs 39714, 39646)

use etcd2 as storage-backend for federation until federation features are completely tested with etcd3

**What this PR does / why we need it**: move federation etcd to etcd3

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #39594

**Special notes for your reviewer**: here is the [link](kubernetes/enhancements#44 (comment)) to announcement making etcd3 as default

**Release note**:

```release-note
```
@madhusudancs madhusudancs mentioned this issue Jan 11, 2017
Closed
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@nikhiljindal nikhiljindal

Labels
area/etcd
Projects
None yet
Milestone
v1.6
4 participants
@madhusudancs @timothysc @shashidharatd @nikhiljindal