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
IBM Turbonomic ARM
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)
Turbonomic on EKS with Turbonomic provided ingress and TLS termination at Load Balancer - Documentation is incomplete/inaccurate
Scenario: Customer is deploying Turbonomic platform on EKS cluster with Turbonomic provided nginx ingress. It needs to terminate TLS at the ELB. Issue with Documentation: The provided documentation at "https://github.com/turbonomic/t8c-install/wiki/4.-Turbonomic-Multinode-Deployment-Steps" provisions a Classic Load Balancer, which is not recommended and has been deprecated by AWS. Also the provisioned load balancer does not work, because after TLS termination at the LB, it tries to send HTTP traffic to HTTPS port on the nginx pod that results into the failure. Workaround solution: I worked with Turbonomic support to workaround this (https://support.turbonomic.com/hc/requests/122619). Below steps were taken to make this scenario working: 1) Turbonomic XL custom resource was updated to provision a Network Load Balancer with a 'http' backend protocol. Below annotations were added for ingress:
global: ingress: annotations: service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing service.beta.kubernetes.io/aws-load-balancer-ssl-cert: <ARN or certificate> service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/aws-load-balancer-type: nlb 2) After Deploying the custom resource, the 'nginx' deployment was modified to set an Environment variable (DISABLE_HTTPS_REDIRECT=true). Turbonomic operator tolerates the environment variables during reconcilation (This should also be indicated in documentation).
Do not place IBM confidential, company confidential, or personal information into any field.