An administrator has deployed the Instana Operator on a Kubernetes cluster and created an InstanaAgent custom resource. Agent pods start but immediately fail to connect to the on-premises Instana backend. The CR spec has the correct agent key configured. Which CR spec field must be set to specify the Instana backend hostname?
Select an answer to reveal the explanation.
Short Explanation and Infographic
In the InstanaAgent Custom Resource Definition managed by the Instana Operator, the backend endpoint hostname is specified using spec.agent.endpointHost and the port using spec.agent.endpointPort. These fields map directly to the agent backend connection configuration and must point to the on-premises backend address. Using incorrect field names results in the agent either failing to connect or attempting to reach a default cloud endpoint instead of the on-premises backend.
Full explanation below image
Full Explanation
In the InstanaAgent Custom Resource Definition managed by the Instana Operator, the backend endpoint hostname is specified using spec.agent.endpointHost and the port using spec.agent.endpointPort. These fields map directly to the agent backend connection configuration and must point to the on-premises backend address. Using incorrect field names results in the agent either failing to connect or attempting to reach a default cloud endpoint instead of the on-premises backend. The correct answer is 'spec.agent.endpointHost'. The incorrect options — 'spec.backend.url', 'spec.connection.hostname', 'spec.instana.serverAddress' — are wrong because they do not align with IBM Instana's architecture or recommended practices for this scenario. Understanding this concept is essential for the Domain 3: Installation domain of the IBM Instana Observability certification.