...
Follow below steps for federation master node. change the default kubernetes config values to make them unique.
By default, we have below kube config after k8s cluster installation:
| Code Block |
|---|
ubuntu@kubefed-1:~$ kubectl config view
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: REDACTED
server: https://10.147.113.131:6443
name: kubernetes
contexts:
- context:
cluster: kubernetes
user: kubernetes-admin
name: kubernetes-admin@kubernetes
current-context: kubernetes-admin@kubernetes
kind: Config
preferences: {}
users:
- name: kubernetes-admin
user:
client-certificate-data: REDACTED
client-key-data: REDACTED
ubuntu@kubefed-1:~$ |
As we intend to use federation cluster as the "host cluster", we added "host" to cluster,user and context names to existing kube config so as to make these names unique.
The initial config view on federation master node after changes will look like below:
| Code Block |
|---|
ubuntu@kubefedubuntu@kubefed-1:~$ kubectl config view apiVersion: v1 clusters: - cluster: certificate-authority-data: REDACTED server: https://10.147.113.131:6443 name: kubernetes-host contexts: - context: cluster: kubernetes-host user: kubernetes-adminhost name: kubernetes-admin-host current-context: kubernetes-admin-host kind: Config preferences: {} users: - name: kubernetes-adminhost user: client-certificate-data: REDACTED client-key-data: REDACTED ubuntu@kubefed-1:~$ |
...