live wire
▸AI · vLLM Recipes maps Muse Spark Open to single-node Blackwell and AMD deployment (Oct. 16)vLLM▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security▸AI · vLLM Recipes maps Muse Spark Open to single-node Blackwell and AMD deployment (Oct. 16)vLLM▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security
upstreambeat.ai
guidePLATFORM

FedRAMP-hosted Red Hat Lightspeed retires October 30—and the replacement changes what users get

Red Hat directs affected organizations to move analytics into Satellite, where host data stays local but the Compliance service is not available.

Timeline of Red Hat Lightspeed retirement and migration steps.
Timeline: dates from the story
By The News Desk· Sep 22, 2026the quick take — two AI hosts go live when you do

Red Hat says the FedRAMP-hosted deployment of Red Hat Lightspeed will be retired on October 30, 2026. A notice in the Red Hat Lightspeed release notes directs affected customers to an on-premises deployment with Red Hat Satellite.

This is more than an endpoint change. Red Hat’s Satellite 6.19 administration guide describes different service boundaries for hosted and in-Satellite Lightspeed. Platform teams should check those boundaries before treating the migration as a like-for-like replacement.

What changes

Hosted Lightspeed sends host data through Satellite to services in the Red Hat Hybrid Cloud Console. The in-Satellite option instead runs the analysis services locally on Satellite Server and does not send reports or Insights client data to the Hybrid Cloud Console.

Both modes provide Advisor recommendations and Vulnerability reporting. Red Hat’s availability table lists Compliance for hosted Lightspeed but not for Lightspeed in Satellite. The documentation also says the hosted console is not limited to those three named services, while an in-Satellite deployment cannot use the hosted services in the Hybrid Cloud Console.

That difference matters for FedRAMP users planning the move: local processing reduces dependence on the hosted service, but it may also change workflows that currently rely on Compliance or other console-hosted capabilities.

What affected teams need to do

Red Hat’s documented migration procedure requires administrators to log Satellite Server into registry.redhat.io, enable the in-Satellite service with satellite-installer, and re-register the Insights client on managed hosts. The installer command depends on whether the local service was enabled previously: Red Hat documents --iop-ensure present for an existing deployment and --enable-iop for a new one.

After migration, administrators should verify that Satellite’s Red Hat Lightspeed menu shows Vulnerability instead of Inventory Upload and confirm that host recommendations still appear. Red Hat notes that the client re-registration step can be executed across hosts with Satellite remote execution.

What to decide now

Affected organizations have just over five weeks from the date of this report to complete the transition. Before changing the deployment, platform and security teams should inventory their use of Compliance and other Hybrid Cloud Console services, confirm that Satellite 6.19’s local service set covers the required workflows, and schedule client re-registration across the managed estate.

The retirement notice is specific to the FedRAMP-hosted deployment. Red Hat’s documentation continues to describe the standard hosted Hybrid Cloud Console integration alongside the in-Satellite option; the notice does not say that every hosted Lightspeed deployment is ending.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk