Merge pull request #6027 from maxlemieux/patch-11

src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure.mdx

@@ -124,7 +124,7 @@ Before starting our [automated installer](https://one.newrelic.com/launcher/k8s-
     system:serviceaccount:<var><namespace></var>:<var><release_name></var>-newrelic-infrastructure
     ```
 
-    The default `<>{'<release_name>'}</>` provided by the installer is `nri-bundle`.
+    The default `<>{'<release_name>'}</>` provided by the installer is `newrelic-bundle`.
     2. Complete the steps in our [automated installer](https://one.newrelic.com/launcher/k8s-cluster-explorer-nerdlet.cluster-explorer-launcher?pane=eyJuZXJkbGV0SWQiOiJucjEtaW5zdGFsbC1uZXdyZWxpYy5ucjEtaW5zdGFsbC1uZXdyZWxpYyIsInBhdGgiOiJndWlkZWQiLCJlbnYiOiJrdWJlcm5ldGVzIiwiaW5pdGlhbEFjdGlvbkluZGV4IjpudWxsLCJhY3Rpb25JbmRleCI6MX0=).
     3. If you're using signed certificates, make sure they are properly configured by using the following variables in the `DaemonSet` portion of your manifest to set the `.pem` file:
 
@@ -177,6 +177,15 @@ If custom manifests have been used instead of Helm, you will need to first remov
 
 We do not recommend applying a new version of the manifest file without removing the previous one first, since it might leave some leftover components in your cluster.
 
+
+## Uninstall Kubernetes integration [#uninstall]
+
+To uninstall the Kubernetes integration using Helm, run the following command. Note that `newrelic-bundle` is the default release name specified by the guided installer.
+
+```shell
+helm uninstall newrelic-bundle -n newrelic
+```
+
 ## Monitor services running on Kubernetes [#services]
 
 After having installed our Kubernetes integration, you can start instrumenting the services than run in your cluster. To learn more about how to do this, please check our [Monitor services running on Kubernetes](/docs/integrations/kubernetes-integration/link-apps-services/monitor-services-running-kubernetes/) page.