> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/frequently-asked-questions/unable-to-modify-existing-default-apiserver-flags.md).

# 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:

{% tabs %}
{% tab title="Command" %}

```bash
# 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>"}'
```

{% endtab %}
{% endtabs %}

## 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/frequently-asked-questions/unable-to-modify-existing-default-apiserver-flags.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
