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 Future consideration
Workspace Instana
Categories Kubernetes Self Hosted
Created by Guest
Created on Dec 23, 2022

Instana on Openshift to use default ingress certificate


We install instana on openshift on my customer environment, customer wants that instana to use default ingress certificate for itself and not give tls.key and tls.crt files again on instana installation on openshift container platform.Because they're already using their own certificates for their openshift and ingress.


Idea priority Medium
  • Admin
    Hubert Hesse
    Mar 3, 2023

    Hi Doruk,

    thank you for your idea. Currently, our agent acceptor needs to terminate TLS in order to have a working connection between Instana backend and agents.

    We plan to use a standard K8s ingress method, which would allow TLS termination by Kubernetes/Openshift. This will as enable you to use the default ingress certificate without giving certificate or private key to the Instana backend.