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

Upgrade path for Stacked HA Controller Nodes #948

Closed
rdodev opened this issue Jun 22, 2018 · 6 comments
Closed

Upgrade path for Stacked HA Controller Nodes #948

rdodev opened this issue Jun 22, 2018 · 6 comments
Assignees
@timothysc @detiber @fabriziopandini
Labels
area/HA area/upgrades kind/documentation Categorizes issue or PR as related to documentation. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
v1.12

Comments

@rdodev
Copy link

rdodev commented Jun 22, 2018

Is this a request for help?

NO

Is this a BUG REPORT or FEATURE REQUEST?

FEATURE REQUEST

Versions

1.11.0-beta.2 ===> 1.11.-rc.1

Description

There's presently not an upgrade path for stacked controller nodes (etcd and control plane on same host). This basically means users going through the trouble of setting up such cluster might find themselves unable to upgrade to new version as they come along.

//cc @timothysc @detiber
@detiber
Copy link
Member

detiber commented Jun 22, 2018

/assign
/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 22, 2018
@detiber
Copy link
Member

detiber commented Jun 22, 2018

/kind documentation
/area HA
/area upgrades

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. area/HA area/upgrades labels Jun 22, 2018
@timothysc timothysc added this to the v1.12 milestone Jun 22, 2018
@schmitch
Copy link

schmitch commented Jun 28, 2018 •
edited
Loading

I could not find any info in the https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md
which feature forbids running a standalone etcd and k8s control plane on the same node (when using kubeadm)?
Edit: Or is this only about the self-hosted etcd?

@timothysc
Copy link
Member

/assign @fabriziopandini

@timothysc timothysc self-assigned this Aug 21, 2018
@fabriziopandini
Copy link
Member

@timothysc @rdodev
If I got this right an upgrade path for stacked etcd is required only if etch version changes. I'm right?
Is this use case expected with v1.12?

@timothysc timothysc added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 19, 2018
@timothysc
Copy link
Member

kubernetes/website#10264 Fixes and deduping with #1044

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

@timothysc timothysc

@detiber detiber

@fabriziopandini fabriziopandini

Labels
area/HA area/upgrades kind/documentation Categorizes issue or PR as related to documentation. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Milestone
v1.12
Development

No branches or pull requests
6 participants
@timothysc @detiber @rdodev @schmitch @fabriziopandini @k8s-ci-robot