> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/33/configure/set-diff-paths-daemon-sets.md).

# Set different paths for Console and Defender (with daemon sets)

When using daemon sets, Console is set up to store the Prisma Cloud config under */opt/twistlock*. By default, it uses this same config when installing the defenders. This article describes a work around solution to be able to set up different config paths for Console and Defenders using daemon sets

1. Download Daemonset configurations for Defender.

   The API to download Daemonset Configuration is:

   ```
   /api/v1/defenders/daemonset.yaml?registry=${registry}&type=${DEFENDER_TYPE}
   &consoleaddr=${consoleaddr}&namespace=${namespace}
   &orchestration=${orchestration}&ubuntu=${os_ubuntu}"
   ```

   The parameters are:

   | registry      | the registry from where Kubernetes gets the image, where you pushed the image. In the example above, the value will be “gcr.io/projectA/”                                                                                                                        |
   | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | type          | defender type - Daemon Set Docker on Linux or Daemon Set Kubernetes Node. (Daemon set Docker on Linux is the regular default Defender type, called in the UI Docker. Only difference being, unlike the default Defender, it does not listen to incoming traffic. |
   | consoleaddr   | Name or IP address that Defenders use to connect to Console.                                                                                                                                                                                                     |
   | namespace     | the default when using the script is twistlock, but you can use whatever you want.                                                                                                                                                                               |
   | orchestration | OpenShift or Kubernetes                                                                                                                                                                                                                                          |
   | ubuntu        | (ubuntu=true \ ubuntu=false), states if the cluster is running on ubuntu OS or not. If not provided, it’s assumed to be false.                                                                                                                                   |
2. Edit the yaml file.

   Make the necessary changes in this yaml file and upload this modified version of the yaml to the K8 controller.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/33/configure/set-diff-paths-daemon-sets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.