Loading

Error "exec: executable kubectl not found" when running rtfctl commands

Veröffentlichungsdatum: Dec 18, 2025
Beschreibung

When attempting to run rtfctl commands (such as rtfctl status or rtfctl report), the operation fails with an error indicating that an executable was not found.

Example Error Output:

time="2025-11-25T11:07:42-05:00" level=warning msg="Failed to create valid RTF context" error="Get \"https://...eks.amazonaws.com/version\": getting credentials: exec: executable kubectl not found
It looks like you are trying to use a client-go credential plugin that is not installed.
Error: no valid kubernetes context provided

Cause This issue occurs because the rtfctl binary relies on the Kubernetes client-go library to authenticate with the cluster. If the kubeconfig file is configured to use an external command for authentication (such as aws-iam-authenticator, kubectl, or an Okta plugin), rtfctl must be able to locate that binary using the system's PATH environment variable.

Even if you can run kubectl manually from the current directory, rtfctl may fail if the directory containing the binary is not explicitly listed in the global system PATH.

Lösung

To resolve this issue, you must add the directory containing the required binary (e.g., kubectl or your specific authentication plugin) to your system's PATH environment variable.

For Windows:

  1. Locate the folder where kubectl.exe (or the missing executable mentioned in the error) is saved.

  2. Press Win + R, type sysdm.cpl, and press Enter.

  3. Navigate to the Advanced tab and click Environment Variables.

  4. Under System Variables (or User Variables), locate the Path variable and click Edit.

  5. Click New and paste the full path to the directory found in Step 1.

  6. Click OK to save changes.

  7. Restart your terminal (Command Prompt or PowerShell) for the changes to take effect.

For Linux / macOS:

  1. Verify the location of your binary:

    ls /path/to/your/binary

  2. Add the directory to your PATH in your shell profile (~/.bashrc, ~/.zshrc, or ~/.bash_profile):

    export PATH=$PATH:/path/to/your/binary

  3. Reload your profile:

    source ~/.bashrc

Verification Open a new terminal window and type the name of the binary (e.g., kubectl) without the file extension or path. If the help text appears, the PATH is configured correctly, and rtfctl should now be able to function correctly.

 

Zusätzliche Ressourcen

For official installation instructions and run commands, please refer to the MuleSoft Documentation:

"The rtfctl command line tool consumes kubeconfig files as described in Organizing Cluster Access Using kubeconfig Files. Use this method to configure which cluster you want to manage. Confirm that the rtfctl binary is present in the current working directory and in the user $PATH."

Nummer des Knowledge-Artikels

005237264

 
Laden
Salesforce Help | Article