File tree Expand file tree Collapse file tree 1 file changed +25
-0
lines changed Expand file tree Collapse file tree 1 file changed +25
-0
lines changed Original file line number Diff line number Diff line change @@ -167,6 +167,31 @@ kubectl -n capo-system logs deploy/capo-controller-manager
167
167
kubectl -n capi-addon-system logs deploy/cluster-api-addon-provider
168
168
```
169
169
170
+ ## Accessing tenant clusters
171
+
172
+ The kubeconfigs for all tenant clusters are stored as secrets. First, you need
173
+ to find the name and namespace of the cluster you want to debug. This can be
174
+ seen from the list of clusters:
175
+
176
+ ``` command title="On the K3s node, targetting the HA cluster if deployed"
177
+ $ kubectl get cluster -A
178
+ ```
179
+
180
+ Then, you can retrieve and decode the kubeconfig with the following:
181
+
182
+ ``` command title="On the K3s node, targetting the HA cluster if deployed"
183
+ $ kubectl -n < namespace> get secret < clustername> -kubeconfig -o json | \
184
+ jq -r ' .data.value' | \
185
+ base64 -d \
186
+ > kubeconfig-tenant.yaml
187
+ ```
188
+
189
+ This can now be used by exporting the path to this file:
190
+
191
+ ``` command title="On the K3s node, targetting the HA cluster if deployed"
192
+ $ export KUBECONFIG=kubeconfig-tenant.yaml
193
+ ```
194
+
170
195
## Zenith service issues
171
196
172
197
Zenith services are enabled on Kubernetes clusters using the
You can’t perform that action at this time.
0 commit comments