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

kube-apiserver instances only rely on a local etcd member #2080

Closed
gdemonet opened this issue Nov 26, 2019 · 0 comments · Fixed by #2181
Closed

kube-apiserver instances only rely on a local etcd member #2080

gdemonet opened this issue Nov 26, 2019 · 0 comments · Fixed by #2181
Assignees
@alexandre-allard
Labels
kind:bug Something isn't working topic:deployment Bugs in or enhancements to deployment stages topic:etcd Anything related to etcd
Milestone
MetalK8s 2.4.2

Comments

@gdemonet
Copy link
Contributor

Component: kubernetes

What happened:

In the manifest for kube-apiserver we deploy, we set the etcd servers only to the local server: --etcd-servers=https://{{ grains.metalk8s.control_plane_ip }}:2379

What was expected:

We should not rely on the fact that we usually deploy etcd next to k-a. Instead, all members should be listed in this --etcd-servers flag, and the manifests should be updated everytime a new member is added/removed to the etcd cluster.
@gdemonet gdemonet added kind:bug Something isn't working topic:deployment Bugs in or enhancements to deployment stages moonshot topic:etcd Anything related to etcd labels Nov 26, 2019
alexandre-allard added a commit that referenced this issue Jan 10, 2020
@alexandre-allard
salt: use all etcd servers as apiserver backends
1234af4 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
@alexandre-allard alexandre-allard mentioned this issue Jan 10, 2020
Merged
alexandre-allard added a commit that referenced this issue Jan 10, 2020
@alexandre-allard
salt: use all etcd servers as apiserver backends
e31f53b 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
alexandre-allard added a commit that referenced this issue Jan 10, 2020
@alexandre-allard
salt: use all etcd servers as apiserver backends
f7b8c9c 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
@alexandre-allard alexandre-allard self-assigned this Jan 10, 2020
alexandre-allard added a commit that referenced this issue Jan 10, 2020
@alexandre-allard
salt: use all etcd servers as apiserver backends
20cfe2b 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
@gdemonet gdemonet added this to the MetalK8s 2.4.2 milestone Jan 16, 2020
Ebaneck pushed a commit that referenced this issue Jan 16, 2020
@alexandre-allard @Ebaneck
salt: use all etcd servers as apiserver backends
3ce865f 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
Ebaneck pushed a commit that referenced this issue Jan 16, 2020
@alexandre-allard @Ebaneck
salt: use all etcd servers as apiserver backends
876e32d 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
Ebaneck pushed a commit that referenced this issue Jan 16, 2020
@alexandre-allard @Ebaneck
salt: use all etcd servers as apiserver backends
1b238c0 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
Ebaneck pushed a commit that referenced this issue Jan 17, 2020
@alexandre-allard @Ebaneck
salt: use all etcd servers as apiserver backends
f232849 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
Ebaneck pushed a commit that referenced this issue Jan 18, 2020
@alexandre-allard @Ebaneck
salt: use all etcd servers as apiserver backends
4a28801 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
alexandre-allard added a commit that referenced this issue Jan 20, 2020
@alexandre-allard
salt: use all etcd servers as apiserver backends
ca15d95 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.
Set the local etcd, if any, as the first member
in the list.

Refs: #2080
alexandre-allard added a commit that referenced this issue Jan 20, 2020
@alexandre-allard
salt: use all etcd servers as apiserver backends
fb17a59 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.
Set the local etcd, if any, as the first member
in the list.

Refs: #2080
Ebaneck pushed a commit that referenced this issue Jan 20, 2020
@alexandre-allard @Ebaneck
salt: use all etcd servers as apiserver backends
244d73b 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.

Refs: #2080
alexandre-allard added a commit that referenced this issue Jan 23, 2020
@alexandre-allard
salt: use all etcd servers as apiserver backends
bb84b6a 
Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.
Set the local etcd, if any, as the first member
in the list.

Refs: #2080
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexandre-allard alexandre-allard

Labels
kind:bug Something isn't working topic:deployment Bugs in or enhancements to deployment stages topic:etcd Anything related to etcd
Projects
None yet
Milestone
MetalK8s 2.4.2
Development

Successfully merging a pull request may close this issue.

salt: use all etcd servers as apiserver backends scality/metalk8s
2 participants
@alexandre-allard @gdemonet