Utilise K8s secrets for InstanaAgent configuration

We are currently using the Instana Agent operator in Red Hat Openshift, and need to configure the Instana Agents. There are several places where use of secrets are in plaintext - this is problematic as we use gitops to manage the configuration of K8s resources, and do not want to put these values into Git.

For example, in this agent YAML we have to specify in plaintext:

• keystore passwords for TLS authentication
• mirror username/passwords for the Instana maven repositories if using local mirroring
• download key for Instana (although maybe necessarily a big problem)

apiVersion: instana.io/v1
kind: InstanaAgent
metadata:
  name: instana-agent
spec:
  agent:
    downloadKey: mydownloadkey
    ...
    configuration_yaml: |
      com.instana.plugin.ibmmq:
        ...
        queueManagers:
          QM1:
            keystore: /opt/instana/agent/etc/instana.jks
            keystorePassword: ************
            cipherSuite: 'TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384'
            channel: INSTANA.A.SVRCONN

    agentReleaseRepoMirrorUrl: 'https://mycompany.com/artifactory/maven-instanafeatures-remote'
    agentReleaseRepoMirrorUsername: mycompanyuser
    agentReleaseRepoMirrorPassword: mycompanypass
    instanaSharedRepoMirrorUrl: 'https://mycompany.com/artifactory/maven-instanashared-remote'
    instanaSharedRepoMirrorUsername: mycompanyuser
    instanaSharedRepoMirrorPassword: mycompanypass

Ideally we would like to be able to point these to a K8s secret name and have the agent pull the values from there instead. This would allow companies to use whatever secrets management tools they wanted to manage/sync K8s secrets separately.