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.
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:
Download the site24x7-agent.yaml file and save it in your Cloud Terminal.
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.
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