From 6b9412830a8ff5fc928d65f34d2d853a519bf6cf Mon Sep 17 00:00:00 2001 From: Matt Liggett Date: Thu, 30 Jun 2016 13:45:13 -0700 Subject: [PATCH] Update details now that we try to make a PV for etcd. --- docs/admin/federation/index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/admin/federation/index.md b/docs/admin/federation/index.md index dee50e33b4..fc077ec839 100644 --- a/docs/admin/federation/index.md +++ b/docs/admin/federation/index.md @@ -86,8 +86,9 @@ Running `federation-up.sh` also creates a new record in our kubeconfig for us to be able to talk to federation apiserver. We can view this by running `kubectl config view`. -Note: `federation-up.sh` creates the federation-apiserver pod with an etcd container that is not backed by any -persistent volume, so it is possible to lose data. You can edit +Note: `federation-up.sh` creates the federation-apiserver pod with an etcd +container that is backed by a persistent volume, so as to persist data. This +currently works only on AWS, GKE, and GCE. You can edit `federation/manifests/federation-apiserver-deployment.yaml` to suit your needs, if required.