Troubleshooting Information
This section describes troubleshooting information for this feature.
Problem
In the multiple AMF deployment scenario, the secondary pods cannot be brought up when the master node has utilized the default pod limit. The secondary pods failed to be up due to one of the following reasons:
-
Pods are in the pending state.
-
The node didn’t match the pod and node affinity or the antiaffinity rules.
Resolution
In circumstances when all the pods are utilized, you can increase the number of pods in the Kubernetes cluster.
To configure the Kubernetes maximum pod count, use the following steps:
On an existing AMF deployment
-
In the SMI Deployer CLI, use the following configuration:
clusters node-defaults k8s max-pods maximum_pods
NOTES:
-
max-pods maximum_pods —Specify the maximum number of pods per node. Default is 256. Must be an integer in the range of 10-2000.
-
-
Assign labels to the nodes within the cluster and sync the changes using the following command:
clusters nodes actions sync run
-
Delete the Istio directory from the master node using the following command:
rm -rf /var/lib/smi/istio/
-
Synchronize the clusters to reflect the configuration using the following commands:
clusters cluster_name actions sync run reset-k8s-nodes true debug true
clusters cluster_name actions sync run sync-phase opscenter debug true
ImportantThe synchronize procedure erases the AMF's day-1 or N configuration.
On a new AMF deployment
-
In the SMI Deployer CLI, use the following configuration:
clusters node-defaults k8s max-pods maximum_pods
NOTES:
-
max-pods maximum_pods —Specify the maximum number of pods per node. Default is 256. Must be an integer in the range of 10-2000.
-
-
Synchronize the clusters using the following commands:
clusters cluster_name actions sync run force-vm-redeploy true debug true
For information on the SMI configuration, see Ultra Cloud Core Subscriber Microservices Infrastructure - Operations Guide.