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)
While the main section heading, 'Enforcing Secure Access Via LDAP' contains clear text stating the subsections are for when you initially installed Turbo, the subsections are not as clear. The first sentence in 8.1.5 or Later for example says it is for a Turbo platform that was installed as version 8.1.5 or later. I think this should be updated to use the same text that is used in the main section and should be in called out clearly with bold and italic text - 'these instructions are for Turbonomic instances that were initially installed before 8.1.5'.
I feel it should also contain instructions to verify as some users will not know when their Turbo instance was originally installed. This can be done by executing a describe on the auth pod to see if the instance is using gluster:
Describe the auth pod and check the volumes
kubectl describe pod auth<TAB>
If you see the following continue using the “8.1.5 or Later: Installing a Self-signed certificate” steps
auth-secret: Type: Secret (a volume populated by a Secret) SecretName: auth-secret Optional: true
If you do not see that please use the “8.1.4 or Earlier: Installing a Self-signed certificate” steps.
Do not place IBM confidential, company confidential, or personal information into any field.