Migrate from traditional Kubernetes monitoring to the OpManager Nexus Kubernetes Operator

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

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. 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. 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 OpManager Nexus 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. 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 OpManager Nexus APM-related environment variables from the application containers.
   4. Apply the updated deployment YAML or redeploy the Helm release.

Step 3: Install the OpManager Nexus Kubernetes Operator

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

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