Skip to Main Content
Cloud Management and AIOps


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 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 Delivered
Workspace IBM Turbonomic ARM
Created by Guest
Created on May 2, 2023

kubeturbo capability to execute rollout command after making change on Deployment Config in OpenShift 3.11 environment

A prospect with a large OpenShift environment has legacy 3.11 clusters which "ConfigChange" triggers are not defined (empty).  In this scenario, k8s will not automatically initiate a rollout with a change that kubeturbo made to the spec template.  This configuration is a platform wide and a prospect is not able to make change.

I would like to request an enhancement for kubeturbo to have an option to execute rollout after making change to the spec template.

https://docs.openshift.com/container-platform/3.11/dev_guide/deployments/basic_deployment_operations.html#triggers

“If no triggers are defined on a deployment configuration, a ConfigChange trigger is added by default. If triggers are defined as an empty field, deployments must be started manually.”

They use below command to rollout manually  - oc rollout latest dc/<deployment-name>

Idea priority High
  • Admin
    Eva Tuczai
    Reply
    |
    Jun 9, 2023

    This capability is in v8.9.2, and will support this DeploymentConfig configuration in both OCP 3.11 and OCP 4.x clusters.