When we use stolon container deployment, we set the parameter wal_keep_segments in the standby cluster: 48 does not take effect

[taoasan]

When we use stolon container deployment, we set the parameter wal_keep_segments in the standby cluster: 48 does not take effect

The configuration information is as follows
echo yes|stolonctl --cluster-name=kube-stolon --store-backend=etcd --store-endpoints=<ETCD_STORE_ENDPOINTS> <CA_VERIFY> init '
{
"role": "standby",
"initMode": "pitr",
"pitrConfig": {
"dataRestoreCommand": "PGPASSWORD=replpassword pg_basebackup -D "%d" -h <master_sa_north_ip> -p 5400 -U repluser -F p -P -X fetch -R"
},
"standbyConfig": {
"standbySettings": {
"primaryConnInfo": "host=<master_sa_north_ip> port=5400 user=repluser password=replpassword",
"standbyMode": "on",
"recoveryTargetTimeline": "latest"
},
"pgParameters" : {"wal_keep_segments": "48"}
}
}'

We set the pgParameters parameter in standbyConfig and want to increase the number of wal logs in the standby cluster, because the default number is only 8, which is too few, and needs to be increased to 48.after the standby cluster is executed. , wal_keep_segments is still 8