Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 updates on 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
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.
Thanks for the latest feedback!
Hi Martin,
I switched to k8s_sensor which solved the requests and limits specification problem. Thanks
Also I discovered that pullSecrets in the Instana_agent section works for k8s_sensor. This is a practical solution, however not documented and bad style from my point of view.
Anyway: issue solved. Ticket can be closed.
In the meantime, if you want to use pullSecrets with the k8sensor, you can still generate a YAML out of Helm with:
helm template --dry-run
and then apply the change manually, just as a workaround.
Hi Andreas!
We are working on the migration documentation and to remove the leader elector from the Helm chart. The k8sensor should be already the default, if it's not the case, please, let me know.
Let me check about secrets and come back to you.
Furthermore, the image for k8sensor does not contain pullSecrets yet! So how can we use our own proxy repository?
Hi Martin, are you saying that the k8sensor replaces the leader elector? But in the helm chart https://github.com/instana/helm-charts/blob/main/instana-agent/values.yaml the leader elector is still there, consuming ressources.
So how is it expected to migrate from leader elector to k8sensor? Do you recommend to just remove the leader elector and add the k8sensor? Is there any documentation on this?
Hello Andreas!
The new k8sensor runs in a different Pod than the agent (not leader election involved anymore) and allows to define specific requests and limits for CPU and Memory.