---
title: "OpenShift"
description: "2 posts about OpenShift, summarised, each linking to the original."
---

# OpenShift
> 2 posts about OpenShift, summarised, each linking to the original.

## Articles

### [Red Hat OpenShift autoscaling using MachineSet autoscaler with KEDA](https://yomu.fyi/post/red-hat-openshift-autoscaling-using-machineset-autoscaler-with-keda.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Ramon Gordillo Gutierrez, Jose Ortiz Padilla
- Published: Sep 1, 2026

The demonstration compares OpenShift MachineSet Autoscaler with KEDA against the previously used Cluster Autoscaler, using metrics to scale a MachineSet before pods remain pending. After installing Red Hat’s Custom Metrics Autoscaler operator (KEDA 2.19), granting permissions for MachineSet scaling and Thanos/Prometheus access, it creates a ScaledObject with a Prometheus trigger targeting demo-p4p95-worker-eastus3. Because a MachineSet has no pods, the HPA path cannot use metricType: Value, so AverageValue is paired with a PromQL query that multiplies CPU request utilization by the current node count. With nine one-CPU test pods, the MachineSet scaled from one to two to three nodes as the metric crossed 75%, and all pods reached Running; two additional Standard\_D4s\_v3 VMs were provisioned in zone 3.


### [AI-powered multicluster management: Querying fleet health with OpenShift Lightspeed and Red Hat Advanced Cluster Management](https://yomu.fyi/post/ai-powered-multicluster-management-querying-fleet-health-with-openshif.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Diego Alvarez Ponce, Luiz Bernardo Levenhagen
- Published: Aug 31, 2026

Managing modern large-scale Kubernetes fleets across distributed clusters can make troubleshooting slow because administrators must build manual search queries and sift scattered outputs. The post presents a Technology Preview MCP server for Red Hat Advanced Cluster Management that translates natural-language prompts into structured searches across managed clusters, deployed with Helm in the hub cluster. OpenShift Lightspeed is configured through its OLSConfig custom resource to call the MCP endpoint, use a Kubernetes service-account token for internal authorization, and optionally skip approval for read-only searches. The examples cover finding clusters below OpenShift 4.21, locating pods in a specified cluster and namespace, and identifying an unhealthy VM across the fleet; one result finds dev-vm in an ErrorUnschedulable condition and provides diagnostic guidance.