K8-Deployment Environment Variables from Kubernetes Secrets should not be visible in process Environment Variables

Introduction:

---------------

Our enterprise company uses instana as a shared open platform for all our developers and teams.

We recently noticed that some of the teams have visible secrets in the process views.
Also, we use strict secret Filtering on the know prominent password field names with the Agent Setup; we can not catch all the secrets which our creative teams define.

After some investigations, we recognized that most of our teams use K8 - Environment Variables in their K8 Deployments to pass their secrets to their applications, for example, database passwords or API keys.

Also, the teams are using K8 Secrets to set the values of their Environment Variables in the k8 deployments definition; they have the problem that instana is making the resulting Environment variables visible in the process view, when our secret pattern is not matching .

Problem:

------------

How to automaticaly make K8s secrets not visible in instana on all levels of infrastructure for a k8 deployment, deploymentconfig (Openshift), CronJob, etc ...?

Desired Solution - > Feature Request:

---------------------

Whenever a K8 Secret is used in an Environment variable for a deployment with:
 -env -> valueFrom: ->  secretKeyRef:
for the corresponding containers, process env variables, JVM args etc. should be handled as secrets to filter.

This is an Enterprise grade needed feature, which all customers will need.

Otherwise Cyber departments will force the teams to disable Environment variables observability completely in there instana agents, as this is the case for us at the moment.