Install Splunk AppDynamics Services in the Hybrid Deployment

Learn how a hybrid deployment uses existing on-premises components while installing services in a Kubernetes cluster.

In a hybrid deployment, the existing on-premises deployment continues to provide standalone Controller, Events Service, and End User Monitoring. The Virtual Appliance cluster hosts the selected services from the following list and securely connects them to the existing Controller and database:

  • Anomaly Detection
  • Secure Application
  • Automated Transaction Diagnostics (ATD)
  • Splunk Log Connect
  • MCP server

For more information to know how hybrid deployment works, see Hybrid Deployment.

Before you Begin

Collect the values below before editing either YAML file. Use production values—examples such as welcome, changeit, and *.nip.io are placeholders only.

Value Example / location Why it is needed
Three Virtual Appliance node IPs 10.0.202.151–153 Cluster initialization, DNS, certificate SANs, Kafka access.
Virtual Appliance ingress domain va.example.com Virtual Appliance UI and service endpoints.
Controller domain and port controller.example.com:8181 Virtual Appliance to-Controller connection.
Controller database host and port Controller host or load balancer; site-specific port Secure Application database access.
Tenant account name customer1 Tenant-specific DNS and authentication routes.
Controller access key Controller UI → Licenses → Account → Access Key Virtual Appliance licensing and authentication.
Controller and database credentials Use a secure secret source Bootstrap and service connectivity.
TLS decision Self-signed or CA-signed Determines which certificate files must be copied.
Virtual Appliance profile small, medium, large, or xlarge Must match the profile used to create the virtual machines.

Installation Workflow

Follow these steps to prepare your environment and install services:
Step 1 Prepare your environment such as cluster, DNS, certificates, configuration, and firewall.
Step 2 Install the standard AppDynamics Services and other selected services.
Step 3 Update the Controller database user, JVM options, and hybrid properties.
Step 4 Restart and verify pods, service Endpoints and agent routing.
  • All nodes use the same time source and have synchronized clocks.
  • The Virtual Appliance can reach the Controller, Controller database, DNS servers, and required package/image sources.
  • The Controller can reach the Virtual Appliance node ports used by Kafka.
  • You have backups and an approved maintenance window for Controller restart.