How to install the Site24x7 agent DaemonSet in a custom namespace
You can achieve the installation of the Site24x7 agent DaemonSet in a custom namespace using two methods:
- Installation using a YAML file
- Installation using Helm
1. Installation using a YAML file
To install the Site24x7 agent DaemonSet in your custom namespace using a YAML file, follow the steps below:
Download the site24x7-agent.yaml file and save it in your Cloud Shell or Master Node terminal.
Create the Secret in that namespace using the command below:
kubectl create secret generic site24x7-agent --from-literal KEY='<device-key>' -n <namespace>
Replace <device-key> and <namespace> with your device key and namespace.
In the Site24x7 agent YAML file, replace the namespace in the highlighted fields:

Execute the command below to apply YAML:
kubectl apply -f site24x7-agent.yaml
By default, kube-state-metrics will be deployed in the kube-system namespace. If necessary, replace the namespace in the highlighted fields in the kube-state-metrics YAML file:


Execute the command below to apply YAML:
kubectl apply -f site24x7-kube-state-metrics.yaml
You have successfully installed the Site24x7 agent DaemonSet in your custom namespace using a YAML file.
2. Installation using Helm
To install the Site24x7 agent DaemonSet in your custom namespace using Helm, follow the steps below:
Download the site24x7-agent.yaml file and save it in your Cloud Shell or Master Node terminal.
Create the Secret in that namespace using the command below:
kubectl create secret generic site24x7-agent --from-literal KEY='<device-key>' -n <namespace>

Replace <device-key> and <namespace> with your device key and namespace.
Use the command below after creating the Secret:
helm repo add site24x7 https://site24x7.github.io/helm-charts/
helm repo update
helm install <Release Name> site24x7/site24x7agent --set kubernetes.namespace=<namespace>
Replace <Release Name> with a release name of your choice for identifying the Helm chart and replace <namespace> with your namespace.
You have successfully installed the Site24x7 agent DaemonSet in your custom namespace using Helm.
Related Articles
How to uninstall the Site24x7 Windows Server Monitoring Agent
Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...
Add Node.js agent in Kubernetes via InitContainers (using prebuilt agent image)
To integrate the APM Insight Node.js agent into your Kubernetes applications using InitContainers, follow the steps given below: Step 1: Create an empty volume that will be used to copy the agent files during the initContainers process. Example: ...
FAQ on Custom Roles
What is the Created permission and what does it allow users to do? The Created permission is a specific type of access control that permits users to perform actions such as View, Write, or Delete solely on the modules, like dashboard, that they have ...
Basic troubleshooting tips for the APM Insight Node.js agent
If you are experiencing issues after installing the APM Insight Node.js agent, follow these troubleshooting tips. Verify agent installation and connectivity To verify the agent installation status, you can execute the following command from the root ...
Bundled .NET and .NET Core agents in a single MSI
In APM Insight .NET agent version 6.8.0, the .NET and .NET Core agents have been bundled into a single MSI, enabling unified monitoring of both application types. Upgrade requirements for .NET Core agent 6.7 and below If you're using .NET Core agent ...