How to move the Kubernetes monitors from one Site24x7 account to another

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. The Kubernetes monitor will be added as a new monitor under the new Site24x7 account and no past data will be available.

 

Solution  

In Site24x7, an account, irrespective of the number of Kubernetes monitors, will have only one device key mapped to it.

 

So, in order to change a Kubernetes agent to point to a particular Site24x7 user account, you have to make a few changes to the agent configuration.

 

You can locate the Device Key of your Site24x7 account by going to Admin > Developer > Device Key. Please make a note of the Device Key of the account to which the monitors are to be migrated.

 

Steps to be followed:  

  1. Download the site24x7-agent.yaml file and save it in your Cloud Terminal.

  2. Execute the below commands to migrate the Kubernetes monitors:

    kubectl delete secret site24x7-agent
    kubectl create secret generic site24x7-agent --from-literal KEY=<new_acc_device_key> && kubectl apply -f site24x7-agent.yaml

 

Once the mapping is complete, you can view the Kubernetes monitors from your new account. You can suspend or delete the Kubernetes monitors from the old account.

 

If you use a custom namespace, replace the namespace in the Site24x7 agent YAML file with your namespace.  

 

 

Customers also search for:

How to add Kubernetes currently monitored by Site24x7 in one account to a different Site24x7 account  

 

 


    • Related Articles

    • Licensing for Kubernetes monitoring

      The main Kubernetes cluster is considered one basic monitor. For the other components, licensing is done as follows: Each node will consume 2 host licenses. The first 10 containers on each host are free. After that, every 10 additional containers ...

    • Licensing for Kubernetes monitoring (old)

      This article contains the licensing model for the customers who signed up before August 2024. Check out this article for more information on the new licensing pattern. Note that the new licensing model applies to users who signed up after August ...

    • How does Site24x7 Kubernetes monitor calculate the memory and CPU utilization for pods?

      Site24x7 Kubernetes Monitor uses the kubelet API and kube-state-metrics API to collect the metrics related to memory and CPU utilization. For memory utilization, the calculation works as follows: Working set size (WSS) memory usage ...

    • Unable to see my Kubernetes resources on the monitor list page

      This case is applicable if your Kubernetes resource monitors are listed in the Kubernetes Monitor List View page instead of Monitor Status listing (Home) page. Site24x7 will not list the Kubernetes resources along with the other monitors on the home ...

    • 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 ...