Troubleshooting installation on Kubernetes

Review the following known issues and troubleshooting tips if you encounter a problem while installing API Connect on Kubernetes

DataPower operator fails to start

DataPower operator fails to start

There is a known issue on Kubernetes that can cause the DataPower operator to fail to start. In this case, the DataPower operator pods can fail to schedule, and display the status message: no nodes match pod topology spread constraints (missing required label). For example:

0/15 nodes are available: 12 node(s) didn't match pod topology spread constraints (missing required label), 
3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.

You can workaround the issue by editing the DataPower operator deployment and reapplying it, as follows:

Delete the DataPower operator deployment, if deployed already:
```
kubectl delete -f ibm-datapower.yaml -n <namespace>
```

Open ibm-datapower.yaml, and locate the topologySpreadConstraints: section. For example:

topologySpreadConstraints:
- maxSkew: 1
  topologyKey: zone
  whenUnsatisfiable: DoNotSchedule

Replace the values for topologyKey: and whenUnsatisfiable: with the corrected values that are shown in the following example:
```
topologySpreadConstraints:
- maxSkew: 1
  topologyKey: topology.kubernetes.io/zone
  whenUnsatisfiable: ScheduleAnyway
```
Save ibm-datapower.yaml and deploy the file to the cluster:
```
kubectl apply -f ibm-datapower.yaml -n <namespace>
```