Help Docs

Migrate from traditional Kubernetes monitoring to the Site24x7 Kubernetes Operator

This document explains how to migrate from a traditional Site24x7 Kubernetes monitoring setup to the Site24x7 Operator-based installation. The migration involves removing the existing Kubernetes monitoring and APM components, and then deploying the Operator-based installation.

Warning

Do not run the traditional node agent and the Operator-managed agent on the same nodes at the same time.

Step 1: Remove existing Kubernetes monitoring

If Kubernetes monitoring is already configured using the traditional installation method, remove the existing deployment before installing the Kubernetes Operator.

For detailed uninstallation instructions, refer to the Kubernetes uninstallation guide.

Step 2: Remove existing APM agent

If APM Insight is already configured in your applications, remove the existing instrumentation before migrating to the operator-based deployment.

Choose the appropriate steps based on your current installation method.

  • If APM was added using a Docker container
    1. Remove all agent files from the application repository.
    2. Remove the existing commands that copy APM Insight agents to the Docker build environment.
    3. Remove APM Insight agent arguments and environment variables from the Dockerfile.
    4. Generate the application image without any APM-related components.
    5. Redeploy the application using the newly generated image.
  • If APM was added using initContainers
    1. Remove the Kubernetes secret created during the APM installation.
    2. Remove the APM-specific initContainer from the deployment YAML or Helm chart.
    3. Remove the associated volume and volumeMount entries from the YAML.
    4. Remove all Site24x7 APM-related environment variables from the application containers.
    5. Apply the updated deployment YAML or redeploy the Helm release.
  • If APM was added using persistent volumes
    1. Remove the Kubernetes secret created during the APM installation.
    2. Remove the persistent volume and volumeMount entries from the deployment YAML or Helm chart.
    3. Remove any Site24x7 APM-related environment variables from the application containers.
    4. Apply the updated deployment YAML or redeploy the Helm release.

Step 3: Install the Site24x7 Kubernetes Operator

After removing the existing Kubernetes monitoring and APM components, install the Site24x7 Kubernetes Operator and deploy the required custom resource configuration.

For complete installation steps and configuration details, refer to the Kubernetes Operator installation help page.

Note

Migrating APM monitoring resources involves a brief period of downtime. This occurs when you restart the required application workloads to allow the newly installed agents to overwrite the existing agents or to add the agents for the first time.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!