While we can use the cluster we had running for the rest of the examples, I would highly recommend that you start fresh. The default naming of the clusters and contexts can be problematic for the federation system. Note that the --cluster-context and --secret-name flags are there to help you work around the default naming, but for first-time federation, it can still be confusing and less than straightforward.
Hence, starting fresh is how we will walk through the examples in this chapter. Either use new and separate cloud provider (AWS and/or GCE) accounts or tear down the current cluster and reset your Kubernetes control environment by running the following commands:
$ kubectl config unset contexts $ kubectl config unset clusters
Double-check that nothing is listed using the following commands:
$ kubectl config get-contexts $ kubectl config get-clusters
Next, we will want to get the kubefed command on our path and make it executable. Navigate back to the folder where you...
