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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following workspace to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Vertical scaling of Application and Event monitoring stateful services
A means by which to effectively perform vertical scaling of key stateful services in the `ibm-cloud-appmgmt-prod` chart.
Today, the stateful services include PersistentVolumeClaims in their pod spec, and use helm values to configure the size of t...
Allow for additional inputs into the placement rules. For example: cost of resources within a cluster, network latency of a cluster (ex: edge vs central cloud), networking capacity between locations, cluster hardware capabilities (CPU pinning, GP...
Enhanced Visibility of Deployed Application Versions.
Update the topology, application, and/or overview screens in MCM to more effectively see what release(s) of applications are deployed to which clusters. These views should be consumable even when there are 100s of clusters and support grouping by...
When doing an application update (such as from v1.0 to v1.1) for multiple Deployables each deployed in their own cluster, the customer needs more control over how those upgrades are performed. The ability to do a canary deployment (upgrade just on...
When doing an application update (such as from v1.0 to v1.1) for a single Deployable, MCM should support Kubernetes rolling upgrades for each service in the application so that the application can be upgraded with zero downtime. Our understanding ...
Add automated provisioning of GRC compliance controllers as part of Install of Klusterlet.
Currently, compliance controllers are not installed as part of the cluster install and there is no automated way to install these controllers hence the GRC does not work out of the box and there is no notification on how to fix it.