Pods are not scheduled
Security pods are not scheduled since the master nodes do not meet the required memory or CPU requirements.
If you are unable to log in to the console, check whether the following pods are scheduled:
auth-idp-xxx auth-apikeys-xxx auth-pap-xxx auth-pdp-xxx secret-watcher-xxx security-onboarding-xxx
If any of these pods are not scheduled, get information about the pod's controller (daemonset, statefulset, deployment, and other components) and check whether the pod is not getting scheduled due to resource unavailability. Use the following command to get the information:
kubectl describe daemonset auth-idp -n ibm-common-services
The output has the information about memory and CPU requirements. If the resource requirement is not met, increase the master node's memory or CPU.
After you increase the resources, the pods are automatically scheduled.