Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Future consideration
Created by Guest
Created on Apr 26, 2024

Increase resiliency of IBM zAPM Connect runtimes in shared Kubernetes environments

In shared Kubernetes environments (clusters hosting multiple application workloads), green zones for node restarts can frequently be continuous or extensive, not tied to a specific application.  Any node may restart at any point for maintenance or platform issues.  To prevent service outages an approach is to require 3+ replicas to allow service continuity when nodes are recycled.   With the current zAPM Connect distributed gateway setup this is an issue since the Kafka and Redis instances are single-pod services.   This idea is to adjust the single-node services in zAPM Connect DG to support microservices (arbitrarily defined here as 2 core, 16 GB RAM resources caps) with multiple pods.  This would increase the service continuity in environments where a scheduled green zone is not feasible.

Idea priority Low