This is an IBM Automation portal for Integration 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
It seems that the APIConnectCluster and AnalyticsCluster CRs do not support injecting environment variables from secrets. We can inject environment variables, just not from secrets.
We are using logstash to offload analytics data. The endpoint that we are offloading data to requires an api key, which is rotated periodically. We are currently hard-coding the api key in the offload config in the AnalyticsCluster CR. When the api-key is rotated, the Secret is automatically updated, but then we need to manually update the AnalyticsCluster CR or else we cannot offload data.
The AnalyticsCR should automatically inject the value of the secret into the pod as an environment variable. This is described here: https://kubernetes.io/docs/tasks/inject-data-application/distribute-credentials-secure/.
Here is some sample configuration from the AnalyticsClusterCR. It assumes there is a secret in the same namespace called `MY_SECRET_OFFLOAD_API_KEY` with a field `api-key`.
spec:
template:
- name: a7s-ingestion
containers:
- name: ingestion
env:
- name: MY_SECRET_OFFLOAD_API_KEY
valueFrom:
secretKeyRef:
name: My-K8s-Secret-Name-Here
key: api-key
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.