> 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/reduce-the-number-of-privilege-escalations-using-sudo-while-exec.md).

# Reduce The Number Of Privilege Escalations Using Sudo While Executing PF9 Scripts/Commands In The Wo

## Problem

In environments where LDAP is configured, it is observed that every command that runs as part of the Nodeletd phases requires a sudo privilege. This is is resulting in high number of ldap lookups even though pf9user is a local user.

{% tabs %}
{% tab title="PF9 scripts using sudo" %}

```javascript
Oct 11 12:00:43 : pf9 : HOST=XXXXXXXXXX : TTY=unknown ; PWD=/ ;
    USER=root ; COMMAND=/opt/pf9/pf9-kube/setup_env_and_run_script.sh
    /opt/pf9/pf9-kube/phases/kubelet_configure_start.sh status
Oct 11 12:00:43 : pf9 : HOST=XXXXXXXXXX : TTY=unknown ; PWD=/ ;
    USER=root ; COMMAND=/opt/pf9/pf9-kube/setup_env_and_run_script.sh
    /opt/pf9/pf9-kube/phases/kube_proxy_start.sh status
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - v5.5 and Higher.

## Answer

This issue is resolved in PMK-5.10.3 release version. The JIRA to track this issue is \[**PMK-6173].**


---

# 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/reduce-the-number-of-privilege-escalations-using-sudo-while-exec.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.