Red HatLena SolarovaAnnouncement
Red Hat Lightspeed advisor self-managed for air-gapped clusters
Summary
Red Hat Lightspeed advisor self-managed, now in Developer Preview, brings health analytics and upgrade risk predictions to air-gapped Red Hat OpenShift clusters. The connected advisor was previously unavailable to disconnected environments because it required uploading data to the Hybrid Cloud Console. The self-managed version runs as a Red Hat Advanced Cluster Management for Kubernetes add-on, with the Insights Operator on each spoke cluster redirecting its archive to a local endpoint on the Hub. The Hub processes the archive in place and displays results in the Red Hat Advanced Cluster Management console, ensuring data never leaves the cluster. Upgrade risk predictions draw from a local Thanos instance on the Hub that holds metrics from spoke clusters.
Context
Organizations operating air-gapped or disconnected Red Hat OpenShift clusters have been unable to use the connected Red Hat Lightspeed advisor, which relies on uploading cluster data to the Hybrid Cloud Console. These clusters face the same infrastructure risks but lack proactive recommendations, misconfiguration flags, and upgrade risk predictions. The new self-managed advisor brings those capabilities into disconnected environments without any data leaving the infrastructure.
Approach / What changed
Red Hat Lightspeed advisor self-managed is delivered as a Red Hat Advanced Cluster Management for Kubernetes add-on. The Insights Operator on each spoke cluster redirects its archive to a local endpoint on the Hub cluster instead of the cloud-based Hybrid Cloud Console. The Hub processes the archive in place and displays results in the Red Hat Advanced Cluster Management console. Upgrade risk predictions draw from a local Thanos instance on the Hub that holds metrics from spoke clusters. The system runs as a single deployment on the Hub cluster, not as a set of microservices.
Takeaways
Red Hat Lightspeed advisor self-managed is delivered as a Red Hat Advanced Cluster Management for Kubernetes add-on and runs as a single deployment on the Hub cluster.
The Insights Operator on each spoke cluster redirects its archive to a local endpoint on the Hub instead of the cloud-based Hybrid Cloud Console, keeping all data within the cluster.
Upgrade risk predictions use a local Thanos instance on the Hub that already holds metrics from spoke clusters, not the archive processing pipeline.
FAQ
How does data flow in the self-managed advisor?
The Insights Operator on each spoke cluster collects anonymized system configuration and redirects it to a local endpoint on the Red Hat Advanced Cluster Management Hub. The Hub processes the archive in place and displays results in the console. No data leaves the cluster.
Why is the architecture a single pod instead of microservices?
The self-managed advisor runs as a single deployment on the Hub cluster, not as a set of microservices. This reduces resource consumption and complexity by consolidating overhead into one pod and replacing network calls with function calls.
How are upgrade risk predictions generated locally?
Upgrade risk predictions draw from a local Thanos instance on the Hub that already holds metrics from spoke clusters, including alerts, operator conditions, and cluster states. This is a second local source separate from the archive processing pipeline.
Source and freshness
- Source
- developers.redhat.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.