A Kubernetes administrator is deploying the Instana agent as a DaemonSet using the standard Instana deployment manifests. A Kubernetes Secret named instana-agent-secret has been created containing the agent key, but agent pods fail to authenticate with the backend. The DaemonSet references the Secret correctly by name. What is the expected data field name within the Secret for the agent key?
Select an answer to reveal the explanation.
Short Explanation
You need the Secret's data field to be named key because the standard Instana agent DaemonSet maps that field to agent authentication. If you use another field name, the agent can't find the key and authentication fails even when the Secret exists.
Full Explanation
The standard Instana agent DaemonSet deployment expects the agent authentication key to be stored in a Kubernetes Secret with the data field name key. The DaemonSet spec references this Secret and maps the key field to the agent authentication configuration. Using alternative field names such as agent key or INSTANA_AGENT_KEY will cause authentication to fail even when the Secret exists and the value is correct. The expected data field name for the agent key is key. The other options are wrong: INSTANA_LICENSE is not the expected data field name for the Instana agent key in the standard DaemonSet manifests, agent key is not the expected data field name, and INSTANA_AGENT_KEY is not the expected data field name either; 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.