Unable to Modify Existing default Apiserver Flags

Problem

Duplicate flags are seen while trying to update/modify the existing Kube-apiserver flag via Qbert API call.

The api call used:

# curl --location --request PUT 'https://<FQDN>/qbert/v4/<Tenant-ID>/clusters/<Cluster-UUID>' --header 'X-Auth-Token: <TOKEN>' --header 'Content-Type: application/json' --data-raw '{"apiServerFlags": "--encryption-provider-config=/var/opt/pf9/kube/apiserver-config/encryption-provider.yaml,--service-account-issuer=https://<Issuer-URL>"}'

Environment

  • Platform9 Managed Kubernetes- v5.11.0

Workaround

  • To prevent duplicate flags, update the master configuration **/opt/pf9/pf9-kube/conf/masterconfig/base/ubuntu/master.yaml** with the correct flags [Add required flags and remove any duplicates].

  • Ensure that there are no other config files containing the same flag in the folder /etc/pf9/kube.d/pod-manifests/ and /opt/pf9/pf9-kube/conf/pod-manifests/ other than master.yaml (e.g., master.yaml_original).

  • Once the necessary changes are made, perform a full stack restart on each node one at a time.

Answer

This is a known issue and is resolved in the PMK-5.12 and PMK-5.11.2 versions.

Additional Information

The Jira used to track this issue is PMK-6637.

© 2025 Platform9. All Rights Reserved

On This Page
Unable to Modify Existing default Apiserver FlagsProblemEnvironmentWorkaroundAnswerAdditional Information