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 (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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Update kubernetes certificate when an instance is upgraded (OVA only issue)
I recently had an issue with a large financial customer where I made a license change and it caused the instance to show that none of the targets were validated any longer. After some troubleshooting, I found a certificate had expired. We worked with support to get it renewed and the instance came back up with all targets validated. When I asked how we could keep the certificate from expiring and taking down a production instance, the only answer was to figure out when it expires and mark it on your calendar to renew it before that date, as there is a script to run that renews it. In discussion with support, they agreed that this is not ideal and that it should be part of the upgrade process. When an instance is upgraded this script should run. Most everyone upgrades at least every year, so this should prevent what happened to me from happening with other customers. Cisco TAC SR 693934805
Do not place IBM confidential, company confidential, or personal information into any field.