Before you begin
You need to have access to the tenant project of the instance. You can get the tenant project id from the customer project id by following these instructions.
You also need to know whether it is a private or public instance. This information can be found in the cluster’s details page under Private cluster, which should be enabled or disabled.
Restarting the pod from command line
Follow the steps in this KB article for connecting to a public or private GKE cluster.
Install kubectl and configure kubectl command line access using steps 1 and 2 in “Getting Getting thread dump” dump section in the same article.
See To see the names of all pods and find the one(s) you want to restart, run the following command:
Code Block kubectl get pods
To restart the pod from the command line:
| Code Block |
|---|
kubectl delete pod <name-of-pod-from-previous-step> |
5. Once the pod(s) has been deleted, rerun command from step 3. You should be able to confirm that the deleted pod has restarted by checking the restarted pod’s age.
Restarting the pod from the UI
In the tenant project, navigate to Kubernetes Engine > Workloads.
...
2. Select the pod that you want to restart. In general, the pod should be named <customer-instance-name>-<pod-type>, i.e. cdap-yuki-demo-appfabric is the appfabric pod for customer instance cdap-yuki-demo.
3. Click “Delete” Delete at the top of the workloads page to delete the pod. It should get automatically restarted.
4. To confirm that the pods are restarting, refresh the page or follow steps 1 - 3 in the previous section.
...
| Page Properties | ||
|---|---|---|
| ||
|