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.

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

Ensure we can upgrade k8 version - in place #33

Open
3 tasks
lewismarshall opened this issue Jun 12, 2017 · 0 comments
Open
3 tasks

Ensure we can upgrade k8 version - in place #33

lewismarshall opened this issue Jun 12, 2017 · 0 comments

Comments

@lewismarshall
Copy link
Collaborator

lewismarshall commented Jun 12, 2017

Note, there maybe no steps required here before going live as keto could just orchestrate new master / compute nodes.

This ticket is more an issue of:

  1. handling upgrades in place without restarting rebuilding nodes
  2. upgrading k8 objects

At the moment keto-k8 shares the manifests using etcd to provide "pre-self hosted" multi-master. At the moment, before self hosted clusters, we would need to introduce k8 version detection on master start (re-share using etcd). - Only some cluster unique pki resources are shared.

This will NOT upgrade essential deployments (proxy or dns) or node configuration which will come after this has been completed:

Steps required:

@lewismarshall lewismarshall changed the title Ensure we can upgrade k8 version Ensure we can upgrade k8 version - in place Jun 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant