Workspace Discovery Commands

Workspaces are managed by a Custom Resource named Workspaces. You can use common kubectl verbs to investigate status and gather log data to help determine any problem areas:

Leverage kubectl to investigate workspace information:
- CODE
```
kubectl get workspaces
```
  OR
- CODE
```
kubectl describe workspace <name>
```

The controller that manages Workspaces is the kommander-cm deployment in the kommander Namespace. Check status logs :

CODE

kubectl describe -n kommander deployment/kommander-cm

OR

CODE

kubectl logs -n kommander deployment/kommander-cm --all-containers --tail -1

Federated* Resources -

Workspace resources federated to Attached clusters are managed by Federated* resources. To view the status of all Federated resources for the Workspace Namespace, we can leverage the following command(s):

CODE

for resource in $(kubectl api-resources | awk '$1 ~ /^federated.*$/ {print $1}'); do kubectl get -n <workspace-namespace> $resource --show-kind --ignore-not-found; done

OR

CODE

kubectl describe -n <workspace-namespace> <resource>

The controller that manages Federated* resources is the kubefed-controller-manager in the kube-federation-system Namespace. It can be helpful to check into the status and logs of the kubefed-controller-manager pod:

CODE

kubectl describe -n kube-federation-system deployment/kubefed-controller-manager

OR

CODE

for pod in $(kubectl get po -n kube-federation-system -lkubefed-control-plane=controller-manager -oname); do kubectl logs -n kube-federation-system $pod --all-containers --tail -1; done

Attached Clusters -
- To check:
  - CODE
```
$body
```
    OR
  - CODE
```
$body
```
- Ensure the status with:
  - CODE
```
$body
```
    OR
  - CODE
```
$body
```
- It can be helpful to check into the status and logs
  - CODE
```
$body
```
    OR
  - CODE
```
$body
```

Next Section

Application Troubleshooting