Skip to Main Content
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
  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 (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.

Status Submitted
Workspace Instana
Categories Kubernetes
Created by Guest
Created on Oct 21, 2025

Method to completely disable the k8sensor deployment when using the instana-agent-operator

Customer would like to a way to disable the k8sensor within the kubernetes agent to manage data ingestion costs. 

The instana-agent-operator ignores the k8s_sensor.deployment.enabled: false configuration.

This k8sensor activity counts towards data ingestion costs (infrastructure metrics) when our configuration clearly specifies APM mode with extensive plugin disablement. We tried the following methods to disable the k8sensor however all are unsuccessful.  

Helm Configuration (provided):

Helm Configuration (provided):
k8s_sensor:
  deployment:
    enabled: false  # COMPLETELY IGNORED
    replicas: 0     # OVERRIDDEN TO default 2

 

K8sensor deployment exists despite enabled: false:

kubectl get deployment instana-agent-k8sensor -n instana-agent
NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
instana-agent-k8sensor   2/2     2            2           100d

 

K8sensor collecting unwanted data:

k8sensor logs: "monitoring=kubernetes entities=4120"

 

Manual intervention fails:

  • Scaling to 0: Operator reverts to 2 replicas within seconds
  • Deleting deployment: Operator immediately recreates
  • Tried 4 different configuration approaches: ALL ignored

The k8sensor is actively monitoring 4,120 Kubernetes resources despite our intention to run APM-only mode.

Idea priority Urgent