Restarting the Management subsystem pods

How to restart Management subsystem pods in your API Connect deployment.

Procedure

Determine your deployment name by running the following command:
```
kubectl -n <namespace> get deployment | grep <management CR>
```
where
- <namespace> is the namespace where the management subsystem is installed.
- <management CR> is the name your management subsystem CR.

Restart pods by running the kubectl commands shown in Table 1.

Use the deployment name that you obtained in step 1.

Table 1. Management pods and the commands to restart them
Pod	Restart command
`management-analytics-proxy`	`kubectl rollout restart deployment/deployment_name -n <namespace>`
`management-apim`	`kubectl rollout restart deployment/deployment_name -n <namespace>` A manual restart is not needed when the certificate is updated.
`management-client-downloads-server`	`kubectl rollout restart deployment/deployment_name -n <namespace>` A manual restart is not needed when the certificate is updated.
`management-atm-api`	`kubectl rollout restart deployment/deployment_name -n <namespace>`
`management-atm-ui`	`kubectl rollout restart deployment/deployment_name -n <namespace>`
`management-juhu`	`kubectl rollout restart deployment/deployment_name -n <namespace>`
`management-ldap`	`kubectl rollout restart deployment/deployment_name -n <namespace>` A manual restart is not needed when the certificate is updated.
`management-lur`	`kubectl rollout restart deployment/deployment_name -n <namespace>` A manual restart is not needed when the certificate is updated.
`management-natscluster`	Run for each `natscluster` pod, one at a time: `kubectl exec management-natscluster-n -- bash -c "kill -HUP 1"` A manual restart is not needed when the certificate is updated.
`edb-operator`	`kubectl rollout restart deployment edb-operator -n <namespace>`
`management-portal-proxy`	`kubectl rollout restart deployment/deployment_name -n <namespace>` A manual restart is not needed when the certificate is updated.
`management-taskmanager`	`kubectl rollout restart deployment/deployment_name -n <namespace>` A manual restart is not needed when the certificate is updated.
`management-tunnel`	`kubectl rollout restart deployment/deployment_name -n <namespace>`
`management-ui`	`kubectl rollout restart deployment/deployment_name -n <namespace>`
`management-analytics-ui`	`kubectl rollout restart deployment/deployment_name -n <namespace>`
`management-remote-sitename-postgres`	`kubectl rollout restart deployment/deployment_name -n <namespace>`

Verify that all management pods are ready by running the following command:
```
kubectl -n <namespace> get pods
```
where <namespace> is the namespace where the management subsystem is installed.

The restart is complete when all pods are Running and Ready.