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 Delivered
Workspace Instana
Categories Extend Capabilities
Created by Guest
Created on Sep 13, 2023

Give Instana Agent helm chart a possiblity to configure the path to containerd.sock

Instana Agent is expecting the containerd.sock in this directory on Kubernetes nodes:


As we are using an RKE2 K8s cluster containerd.sock is located in /run/k3s/containerd/containerd.sock instead which results in instana-agent pods not being able to use containerd and therefore not working properly, especially with PHP tracing.

Here is documentation that shows that RKE2 places containerd.sock /run/k3s/containerd/containerd.sock

This means that the instana-agent is not working properly on an RKE2 environment.

It would be great if a variable in the instana-agent helm chart can be added to state where the containerd.sock is located. As of now we need to create symlinks on every K8s Node for it. Unfortunately these symlinks are lost when the nodes or rancher services restart.

Idea priority High
  • Admin
    Henning Treu
    Jan 12, 2024


    this should be resolved with Agent bundle 1.1.702, released Nov 9th, 2023.

    Best regards

    Henning Treu - Instana Product Manager Agent, Logging, Applications