> 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/content-collections/runtime-security/upgrade/upgrade-daemonset.md). # Manually Upgrade Defender DaemonSets Upgrade the Defender DaemonSets in your environment. ## Upgrade the Defender DaemonSets with twistcli (Kubernetes) Delete the Defender DaemonSet, then rerun the original install procedure. **Prerequisites:** You know all the parameters passed to *twistcli* when you initially deployed the Defender DaemonSet. You’ll need them to recreate a working configuration file for your environment. 1. Delete the Defender DaemonSet. ```sh $ kubectl -n twistlock delete ds twistlock-defender-ds $ kubectl -n twistlock delete sa twistlock-service $ kubectl -n twistlock delete secret twistlock-secrets ``` 2. Retrive Console’s API address (PRISMA\_CLOUD\_COMPUTE\_CONSOLE\_URL). 1. Sign into Prisma Cloud. 2. Go to **Runtime Security > Manage > System > Utilities**. 3. Copy the URL under **Path to Console**. 3. Retrieve Console’s hostname (PRISMA\_CLOUD\_COMPUTE\_HOSTNAME). The hostname can be derived from the URL by removing the protocol scheme and path. It is simply the host part of the URL. You can also retrieve the hostname directly. 1. Go to **Runtime Security > Manage > Defenders > Deploy > Defenders > Orchestrator** 2. Copy the hostname from **Step 3** (**The name that Defender will use to connect to this Console**) 4. Generate a *defender.yaml* file, where: The following command connects to Console (specified in *--address*) as user \ (specified in *--user*), and generates a Defender DaemonSet YAML config file according to the configuration options passed to *twistcli*. The *--cluster-address* option specifies the address Defender uses to connect to Console. ``` $ /twistcli defender export kubernetes \ --user \ --address https://yourconsole.example.com:8083 \ --cluster-address twistlock-console ``` * \ can be linux, osx, or windows. * \ is the name of a Prisma Cloud user with the System Admin role. 5. Deploy the Defender DaemonSet. ```sh $ kubectl create -f defender.yaml ``` 6. In Prisma Cloud, go to **Runtime Security > Manage > Defenders > Manage > DaemonSets** to see a list of deployed Defenders. ## Upgrade the Defender DaemonSets with twistcli (OpenShift) Delete the Defender DaemonSet, then rerun the original install procedure. **Prerequisites:** You know all the parameters passed to *twistcli* when you initially deployed the Defender DaemonSet. You’ll need them to recreate a working configuration file for your environment. 1. Delete the Defender DaemonSet. ```sh $ oc -n twistlock delete ds twistlock-defender-ds $ oc -n twistlock delete sa twistlock-service $ oc -n twistlock delete secret twistlock-secrets ``` 2. Retrive Console’s API address (PRISMA\_CLOUD\_COMPUTE\_CONSOLE\_URL). 1. Sign into Prisma Cloud. 2. Go to **Runtime Security > Manage > System > Utilities**. 3. Copy the URL under **Path to Console**. 3. Retrieve Console’s hostname (PRISMA\_CLOUD\_COMPUTE\_HOSTNAME). The hostname can be derived from the URL by removing the protocol scheme and path. It is simply the host part of the URL. You can also retrieve the hostname directly. 1. Go to **Runtime Security > Manage > Defenders > Deploy > Defenders > Orchestrator** 2. Copy the hostname from **Step 3** (**The name that Defender will use to connect to this Console**) 4. Generate a *defender.yaml* file, where: The following command connects to Console (specified in *--address*) as user \ (specified in *--user*), and generates a Defender DaemonSet YAML config file according to the configuration options passed to *twistcli*. The *--cluster-address* option specifies the address Defender uses to connect to Console. ``` $ /twistcli defender export openshift \ --user \ --address https://yourconsole.example.com:8083 \ --cluster-address twistlock-console \ --selinux-enabled ``` * \ can be linux, osx, or windows. * \ is the name of a Prisma Cloud user with the System Admin role. 5. Deploy the Defender DaemonSet. ```sh $ oc create -f defender.yaml ``` 6. In Prisma Cloud, go to **Runtime Security > Manage > Defenders > Manage > DaemonSets** to see a list of deployed Defenders. ## Upgrade the Defender DaemonSets from Console Upgrade the Defender DaemonSets directly from the Console UI. If you can’t access your cluster with kubectl or oc, then you can upgrade Defender DaemonSets directly from the Console UI. **Prerequisites:** You’ve created a [kubeconfig credential](/content-collections/runtime-security/authentication/credentials-store/kubernetes-credentials.md) for your cluster so that Prisma Cloud can access it to upgrade the Defender DaemonSet. 1. Log into Prisma Cloud Console. 2. Go to **Manage > Defenders > Manage**. 3. Click **DaemonSets**. 4. For each cluster in the table, click **Actions > Upgrade**. The table shows a count of deployed Defenders and their new version number. --- # 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/content-collections/runtime-security/upgrade/upgrade-daemonset.md?ask=&goal= ``` `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.