Instana agent

Instana Agent gathers information about the systems and applications it can observe and sends that telemetry to an Instana monitoring backend. It helps teams investigate service behavior with context from the infrastructure underneath. On Kubernetes, the installation needs the correct node access, identity and backend connection to provide that coverage. Deploying the agent alone does not create the receiving monitoring service or establish that every intended application is reporting useful data.

Current guidance

The historical stable/instana-agent chart is deprecated. IBM now documents installation through its agent Helm chart or operator, including online and air-gapped environments. The current project chart deploys the operator internally and creates an Agent custom resource. The agent sends telemetry to an Instana backend; deploying its pods alone does not provide that backend or establish subscription entitlement.

Follow the current installation guide for the selected cluster environment. Check the agent key, backend endpoint, cluster name, required RBAC and node access before rollout. Review the agent’s reach into host workloads against your cluster’s security policy, and ensure sensitive credentials are managed through an appropriate Secret workflow.

IBM’s administration guide treats chart or operator upgrades and image updates separately. Record the chart, operator and image versions. Apply the selected chart’s required custom-resource definition updates before the Helm upgrade: the project README states that Helm does not apply these CRD updates automatically. For an air-gapped setup, verify the mirrored agent, sensor and controller images and their update process. Validate node coverage, outbound connectivity and representative service telemetry before expanding the rollout. This source review does not certify a specific cluster, image digest or compatibility combination.