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

MESOS: Document package default for etcd persistence #18355

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions contrib/mesos/docs/issues.md
Expand Up @@ -198,6 +198,16 @@ The scheduler also offers `/debug` API endpoints that may be useful:
All of the issues in the above section also apply to the Kubernetes-Mesos DCOS package builds.
The issues listed in this section apply specifically to the Kubernetes-Mesos DCOS package available from https://github.com/mesosphere/multiverse.

### Etcd

The default configuration of the DCOS Kubernetes package launches an internal etcd process **which only persists the cluster state in the sandbox of the current container instance**. While this is simpler for the first steps with Kubernetes-Mesos, it means that any cluster state is lost when the Kubernetes-Mesos Docker container is restarted.

Hence, for any kind of production-like deployment it is highly recommended to install the etcd DCOS package alongside Kubernetes-Mesos and
configure the later to use the etcd cluster. Further instructions
can be found at https://docs.mesosphere.com/services/kubernetes/#install.

This situation will eventually go away as soon as DCOS supports package dependencies and/or interactive package configuration.

### Kubectl

The following `kubectl` and `dcos kubectl` commands are not yet supported:
Expand Down