From 626bdd1f3ccaece73a4529fa5e553a0615479122 Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Mon, 17 Apr 2017 15:23:41 -0700 Subject: [PATCH] kubefed tutorial: add creating the default ns (#3105) Currently kubefed does not create the default namespace, therefore anyone following this doc today will hit this issue. Adding a few comments to bridge that gap until the bug is fixed. Signed-off-by: Ahmet Alp Balkan --- .../set-up-cluster-federation-kubefed.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/tutorials/federation/set-up-cluster-federation-kubefed.md b/docs/tutorials/federation/set-up-cluster-federation-kubefed.md index 6e5518b63d..926d4d4154 100644 --- a/docs/tutorials/federation/set-up-cluster-federation-kubefed.md +++ b/docs/tutorials/federation/set-up-cluster-federation-kubefed.md @@ -123,6 +123,20 @@ The domain suffix specified in `--dns-zone-name` must be an existing domain that you control, and that is programmable by your DNS provider. It must also end with a trailing dot. +Once the federation control plane is initialized, query the namespaces: + +```shell +kubectl get namespace --context=fellowship +``` + +If you do not see the `default` namespace listed (this is due to a +[bug](https://github.com/kubernetes/kubernetes/issues/33292)). Create it +yourself with the following command: + +```shell +kubectl create namespace default --context=fellowship +``` + The machines in your host cluster must have the appropriate permissions to program the DNS service that you are using. For example, if your cluster is running on Google Compute Engine, you must enable the