Skip to Main Content
Cloud Management and AIOps

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace Instana
Categories Agent
Created by Guest
Created on Jul 13, 2022

Deploy different instana-agent.customresource.yaml in k8s worker nodes


Based on the fact that not all the worker nodes run the same applications and ca be different between each others, it can be needed yo deploy different configuration.yaml files based on the needs.

For example, put some custom tags inside some specific hosts, enable or disable some plugins, setting some credentials only to those nodes where the applications wanted are running and so on.

Is there any possibility to work on the request being able to deploy different configuration files per node?


Idea priority High
  • Guest
    Oct 17, 2022


    I do not agree with the status and the feedback provided. Based on your statement: "typically in Kubernetes nodes have no special meaning since the scheduler can move workloads between nodes freely. This is not under consideration." it is somehow general and does not fit with our current k8s architecture.

    We have some worker nodes to be used for specific purposes (Monitoring, NoSQL, BSS Stack and so on) setting with affinity / anti-affinity which pods are deployed here and there.

    Please reconsider the status of this idea on the same way we can define different instana configuration file based on dockerzied or services architecture.


  • Admin
    Henning Treu
    Sep 29, 2022

    Dear Customer,
    We thank you so much for submitting an idea and, in doing this, we appreciate your support in improving Instana product.
    Unfortunately this requirement is not currently in our roadmap and will not be for the next 12/18 months.
    If this feature is still a priority for your Instana implementation at that time, please reopen it to bring up to our attention and we will reevaluate for its inclusion.

    Additional information: typically in Kubernetes nodes have no special meaning since the scheduler can move workloads between nodes freely. This is not under consideration.

    Best regards
    Henning Treu - Product Manager Instana Agent & Application Perspectives