Pods stop running when PCF is upgraded through the Rolling Upgrade process
This section describes how to ensure that the pods are running when PCF is upgraded.
Problem
When the PCF version is upgraded to the subsequent available version, some pods such as CRD and Policy Engine stop running.
Resolution
Whenever you configure PCF ensure that you configure the following parameters:
-
db global-settings db-replica replica_count
-
db spr shard-count shard_count
-
rest-endpoint ips ip_address1, ip_address2, ip_address3
-
rest-endpoint port port_number
-
engine engine_name
replicas replica_count
unified-api-replicas api_replica_count
subversion-run-url repository_url
subversion-config-url configuration_url
tracing-service-name service_name
-
service-registration profile locality profile_name
-
service-registration profile plmn-list [ mcc mnc ]
-
service-registration profile snssais [ sst sd ]