Considerations
This feature has the following considerations in this release:
-
If the AMF deployment scenario has multiple servers, the servers must be labeled. The labeling is helpful when one of the server nodes is faulty or out of service.
You can label the servers as:
-
Server1: Labeled for protocol and service layer pods
-
Server2: Labeled for service and datastore layer pods
-
Server3: Labeled for datastore and protocol layer pods
-
-
When multiple instances of AMF are deployed on the servers, and these servers do not have sufficient hardware resources (CPU cores, memory), then you can reset the default pod limit prescribed by Kubernetes.
You can scale the number of pods by using the following configuration in the SMI Deployer CLI:
clusters cluster name node-defaults k8s max-pods number_of_pods