Adding a guide for admins to set up federation #656
Conversation
| ```shell | ||
| $ kubectl get clusters --context=federation-cluster | ||
| NAME STATUS VERSION AGE | ||
| cluster1 Ready 3m |
There was a problem hiding this comment.
FYI, I havent been able to reach this state. My cluster remains in "Offline" state. I see the following in my controller manager logs:
E0613 03:29:22.404990 1 cluster_client.go:147] Failed to list nodes while getting zone names: the server could not find the requested resource
W0613 03:29:22.405017 1 clustercontroller.go:194] Failed to get zones and region for cluster cluster1: the server could not find the requested resource
Am still debugging it
There was a problem hiding this comment.
This was a config problem with my setup.
Works great now!
|
cc @lavalamp who also had suggestions on making this easier for admins to setup |
|
cc @kubernetes/docs @kubernetes/docs-review-team @johndmulhausen Can you please confirm that this is the right way to create a doc now? |
|
This is part of 1.3 docs |
|
The placeholders in the main repo are only for auto-generated documents. I thought we copied docs from there to here ~each release. @johndmulhausen would know if the canonical doc should be here or there. |
|
@nikhiljindal Needs to go into the release-1.3 branch |
|
@bgrant0607 So I need to move this PR to the core kubernetes repo? Last time I created a PR there I was told that only auto generated docs are accepted there. All other docs should be edited directly here: kubernetes/kubernetes#26313. |
|
@nikhiljindal: I guess @bgrant0607 says the branch release-1.3 in this repo. |
|
aah thanks @rata Hadnt noticed the branch in this repo :) @johndmulhausen The edit instructions are geared towards editing existing docs. We should add instructions for adding docs. Sent #662 for branch release-1.3. |
Automatic merge from submit-queue Updating federation up scripts to work in non e2e setup Ref: kubernetes/website#656 Updating the federation up scripts so that they work as per steps in kubernetes/website#656. Changes are: * Updating the default namespace to be "federation" instead of "federation-e2e" * Updated the kubeconfig context to be named "federation-cluster" instead of "federated-context" * Fixing federation-up so that FEDERATION_IMAGE_TAG is set even when federation-up is run without running `e2e.go --up`. e2e-up.sh sets it here: https://github.com/kubernetes/kubernetes/blob/6a388d4a0d9e7fc2549ab89c97bf29ce53982e39/hack/e2e-internal/e2e-up.sh#L44. * Adding a "missingkey=zero" option to template parser. Without this, the parser adds `"<no value>"` at the place of an env var that is not set. With this change, it instead replaces it with the corresponding zero value (for ex "" for strings). This is required for the FEDERATION_DNS_PROVIDER_CONFIG env var. cc @kubernetes/sig-cluster-federation @colhom @mml
|
The edit docs page does include the necessary details on adding pages. See: "Edit Page Titles or Change the Left Navigation" -- definitely will need to add a left nav entry for this file. And yes, please ensure release-1.3 is the target for any Kubernetes 1.3 docs. |
| Now that we have the federation control plane up and running, we can start registering kubernetes clusters. | ||
|
|
||
| First of all, we need to create a secret containing kubeconfig for that kubernetes cluster, which federation control plane will use to talk to that kubernetes cluster. | ||
| For now, we create this secret in the host kubernetes cluster (that hosts federation control plane). When we start supporting secrets in federation control plane, we will create this secret their. |
There was a problem hiding this comment.
fixed in #662, thx!
|
One important thing that isn't included here is how DNS works. Right now AWS and GCE are supported, but the docs don't mention how/why DNS is used, or how users can add their own DNS provider. Another thing that isn't clear is whether resources - like pods or services - can exist at the federation level, i.e. in the |
|
|
||
| ``` | ||
|
|
||
| By specifying `--cluster=federation-cluster`, we direct the request to federation apiserver. |
There was a problem hiding this comment.
this should be --context right?
There was a problem hiding this comment.
yes, fixed in #662, thx!
|
Thanks for your comments @jamiehannaford |
Automatic merge from submit-queue Updating federation up scripts to work in non e2e setup Ref: kubernetes/website#656 Updating the federation up scripts so that they work as per steps in kubernetes/website#656. Changes are: * Updating the default namespace to be "federation" instead of "federation-e2e" * Updated the kubeconfig context to be named "federation-cluster" instead of "federated-context" * Fixing federation-up so that FEDERATION_IMAGE_TAG is set even when federation-up is run without running `e2e.go --up`. e2e-up.sh sets it here: https://github.com/kubernetes/kubernetes/blob/6a388d4a0d9e7fc2549ab89c97bf29ce53982e39/hack/e2e-internal/e2e-up.sh#L44. * Adding a "missingkey=zero" option to template parser. Without this, the parser adds `"<no value>"` at the place of an env var that is not set. With this change, it instead replaces it with the corresponding zero value (for ex "" for strings). This is required for the FEDERATION_DNS_PROVIDER_CONFIG env var. cc @kubernetes/sig-cluster-federation @colhom @mml
cc @kubernetes/sig-cluster-federation @colhom @mml
Guide with steps for admin to setup federation