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
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
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, use the below command:
helm repo add site24x7 https://site24x7.github.io/helm-charts;
helm repo update;
helm install site24x7-agent site24x7/site24x7 -n <namespace> --set deviceKey=<device-key>;
Replace the<device-key> with your device key and <namespace> with your namespace.Related Articles
How to uninstall the Site24x7 Kubernetes monitoring agent
Execute the below commands to uninstall the Site24x7 Kubernetes monitoring agent from your cluster: Deletion command for the DaemonSet agent deployed using a YAML file: kubectl delete -f site24x7-agent.yaml or kubectl delete ds,sa site24x7-agent -n ...How to migrate Kubernetes monitors from one Site24x7 account to another
Use case An existing Site24x7 user has Kubernetes monitoring in a Site24x7 account and plans to migrate his Kubernetes monitors to a different account. The historic data and the current display name of the Kubernetes monitors will not be migrated. ...List of log files generated and maintained by the Site24x7 server monitoring agent
Here is the list of log files generated by the Linux and Windows server monitoring agent. The log files are stored in the same directory where the agent source file is installed. By default they are at: For Linux : ...Licensing for Kubernetes monitoring
The licensing for the Kubernetes monitors is as follows: Component Licensing Cluster One cluster monitor consumes one basic monitor license Nodes One node monitor consumes two host licenses* *The first 10 containers on each node are free. After that, ...Steps to install Linux monitoring agent in custom platforms/distributions
If you want to install the Site24x7 Server Monitoring agent in platforms/flavors other than Debian, Ubuntu, CentOS, RedHat, Madriva, Fedora, Suse, Amazon Linux, Gentoo, CoreOS, Raspberry Pi (requires Python 3 and above), ARM Processor (requires ...