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 Planned for future release
Workspace IBM Turbonomic ARM
Created by Guest
Created on Jan 25, 2024

KubeTurbo helm chart - enable a toleration

Hello,

I have an enhancement request for the KubeTurbo helm chart, which is here: https://github.com/turbonomic/kubeturbo/tree/master/deploy/kubeturbo-operator/helm-charts/kubeturbo

The ask is to please add the ability to include a toleration in the deployment, using a value passed into the helm chart. That is, add an option in the values.yaml file that lets us pass a toleration or set of tolerations for the kubeturbo deployment.

Even better would be to add the ability to add options for both a toleration and an affinity.

This is about taints and tolerations: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

This is about affinity: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

The business reason we need this is that AKS clusters have at least two node pools as a best practice:

1. A system node pool which has the taint CriticalAddonsOnly=true:NoSchedule

    - Ideally KubeTurbo would be able to run on this node pool. This requires a toleration of that taint.

    - Info: https://learn.microsoft.com/en-us/azure/aks/use-system-pools?tabs=azure-cli

2. And a user node pool where end-user applications run

The system node pool is there to enable system utilities like KubeTurbo to run without competing with applications for resources.

 

Thank you

Idea priority Medium
  • Admin
    Murtuza Mukadam
    Reply
    |
    Mar 13, 2024

    Hello Mary, thank you for submitting this Idea. We have discussed this with the team and will be considering this enhancement for a future release. We will reach out to you for more details.

  • Admin
    Jason Shaw
    Reply
    |
    Jan 29, 2024

    Thanks Mary for taking the time to submit this Idea. Appreciate the specific details as well, this is very helpful, I will review this further with my team, thanks