Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Needs more information
Created by Guest
Created on Aug 3, 2026

Lack of Kubernetes-Native Resource Management


Current State

IBM EEM does not provide Kubernetes Custom Resource Definitions (CRDs) or Custom Resources (CRs) for managing core platform components. Unlike other IBM Event Automation products, such as IBM Event Streams, which leverage Strimzi CRDs (KafkaConnect, KafkaTopic, KafkaUser, etc.), EEM lacks a declarative Kubernetes-native resource model( roadmap from vendor moving to have CRD based in future release)

As a result, significant custom automation has been required to bridge this gap.


 

Component 

Kubernetes-Native Approach (Expected) 

What We Had to Build 

Gateway Deployment 

CR like EventGateway without ingress dependency  

Manual StatefulSet, ConfigMap, NLB, Service, PDB via Terraform 

Cluster Registration 

CR like KafkaCluster with connection details 

Shell script calling POST /admin/clusters with mTLS cert extraction from K8s secrets 

Event Sources 

CR like EventSource with topic mapping 

Shell script calling POST /admin/eventsources with idempotency checks 

Virtual Topics (Options) 

CR like VirtualTopic with mTLS controls 

Shell script calling POST /admin/options with JSON payload construction 

CA Certificates 

Mounted as K8s secrets, auto-discovered 

Shell script iterating files and calling POST /admin/profile/ca and /admin/organization/ca 

Applications 

CR like EventApplication with subscriptions 

Not automatable at all (manual UI only) 

TLS Certificates 

Managed by operator 

External cert-manager Certificate CR with Venafi ClusterIssuer 

NLB/DNS 

Managed by operator or annotations 

Separate Terraform resources (aws_lb, aws_route53_record, TargetGroupBinding) 

Idea priority Low
  • Admin
    Salma Saeed
    Aug 6, 2026

    On our near term roadmap, we plan to support a Kubernetes way of describing topics, clusters, virtual topics, etc. To help us deliver this in a way that meets your needs, it would be useful to understand the K8 native approach expected for Gateway Deployment. In the idea it asks for "CR like EventGateway without ingress dependency". Could you please elaborate on the requirement? Thank you.