Install Virtual Appliance with external services

Enable external services mode, install Splunk AppDynamics Virtual Appliance, and verify the deployment.

1. Enable external services mode in config/globals.yaml.gotmpl.
   CODECopy

   externalizeServices: enabled: true

   externalizeServices:
     enabled: true

   Important: The value must be the unquoted YAML true.
2. Confirm the target cluster and install Virtual Appliance from the package root.
   CODECopy

   kubectl config current-context kubectl cluster-info appdcli start all

   kubectl config current-context
   kubectl cluster-info
   appdcli start all

   Use the same profile that you used to size the external services.

   If a prerequisite check fails, correct the reported service or configuration problem and run the same installation command again.

3. Check Helm releases, Jobs, pods, and warning events.
   CODECopy

   helm list -A kubectl get jobs,pods -A kubectl get events -A --field-selector type=Warning --sort-by=.metadata.creationTimestamp

   helm list -A
   kubectl get jobs,pods -A
   kubectl get events -A --field-selector type=Warning --sort-by=.metadata.creationTimestamp

4. Verify Kubernetes resources.
   • External adapters and bridge releases are installed.
   • Validator, bootstrap, and schema Jobs completed.
   • Required credential and CA Secrets exist in consumer namespaces without exposing their values.
   • Application pods are ready and stable.
   • Embedded service operators, StatefulSets, and data persistent volume claims were not installed.
5. Verify Kafka and PostgreSQL from the service side.
   • Confirm that connections use TLS and originate from the expected OpenShift addresses.
   • Confirm that no authentication or authorization failures occur.
   • Confirm that Kafka topics and ACLs remain valid and that brokers have sufficient capacity.
   • Confirm that the PostgreSQL writer is writable, application schemas exist, and the database has sufficient capacity.
6. Verify MySQL after installation.
   • Confirm that the mysql-external release is deployed and that no AppDynamics MySQL database pods or data volumes were created.
   • Confirm that required application workloads and bootstrap jobs are healthy.
   • Confirm that application schemas contain tables and that application sessions use TLS.
   • Monitor connections, CPU, memory, storage, latency, backups, failover, authentication failures, and certificate expiry.
7. Verify MinIO after installation.
   • Confirm that the required buckets and lifecycle rules exist.
   • In administrator mode, confirm that the expected consumer identities exist.
   • Confirm that the required MinIO credential and CA Secrets exist in the EUM, Synthetic Monitoring, and Secure Application namespaces without decoding them.
   • Confirm that the consumer workloads are ready and can read and write objects over TLS.