This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
K8-Deployment Environment Variables from Kubernetes Secrets should not be visible in process Environment Variables
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 .
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.
Do not place IBM confidential, company confidential, or personal information into any field.