# Red Hat

Stories and tutorials on the latest technologies in cloud application development.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9

DevFeed: [The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9](<https://devfeed.tech/articles/the-ultimate-guide-to-analyzing-and-troubleshooting-critical-issues-on-red-hat-enterprise-linux-8-and-9-144332.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/19/ultimate-guide-to-troubleshooting-critical-issues-on-rhel-8-and-9>)

Author: Kailash Nailwal

Published: 2026-11-19T14:16:41Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [rhel](<https://devfeed.tech/topics/rhel.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [SELinux](<https://devfeed.tech/topics/selinux.md>)

Tags: [blink](<https://devfeed.tech/tags/blink.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [business-operations](<https://devfeed.tech/tags/business-operations.md>), [core](<https://devfeed.tech/tags/core.md>), [critical](<https://devfeed.tech/tags/critical.md>), [devops](<https://devfeed.tech/tags/devops.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [environment](<https://devfeed.tech/tags/environment.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hat](<https://devfeed.tech/tags/hat.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [observability](<https://devfeed.tech/tags/observability.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-enterprise](<https://devfeed.tech/tags/red-hat-enterprise.md>), [red-hat-enterprise-linux](<https://devfeed.tech/tags/red-hat-enterprise-linux.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

The guide recommends disciplined, evidence-preserving triage for critical RHEL 8 and 9 outages: establish host identity and incident timing, then check CPU, memory, storage, services, networking, logs, security controls, time, resource limits, package history, and hardware for correlated symptoms. It gives commands and observables for each area, with cautions such as distinguishing load from CPU use, static swap from active paging, and ping reachability from application-port availability; it also warns against blind filesystem repairs or globally disabling SELinux. For crashes, it covers `kdump` and `coredumpctl`; for support, it recommends an incident-time `sosreport`, chronological context, logs, and relevant core dumps or SAR data. The text notes that enterprise deployments may need tailored procedures.

### Source excerpt

When a critical outage hits a production environment, time is your most crucial resource. Systems going down, unresponsive microservices, kernel panics, or sudden I/O bottlenecks can quickly jeopardize core business operations. For systems administrators, site reliability engineers (SRE), and DevOps teams managing enterprise workloads on Red Hat Enterprise Linux 8 or 9 (RHEL), having a disciplined and reproducible standard operating procedure (SOP) is what separates a blink from a catastrophe. The post The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9 appeared first on Red Hat Developer.

## Automate Spring 5.3.x CVE remediation with Lightwell

DevFeed: [Automate Spring 5.3.x CVE remediation with Lightwell](<https://devfeed.tech/articles/automate-spring-5-3-x-cve-remediation-with-lightwell-144329.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/19/automate-spring-5-3-x-cve-remediation-lightwell>)

Author: Vivek Koul, Shailendra Kumar Singh

Published: 2026-11-19T14:16:40Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Spring Framework](<https://devfeed.tech/topics/spring-framework.md>), [ibm red hat project lightwell](<https://devfeed.tech/topics/ibm-red-hat-project-lightwell.md>), [Spring Boot](<https://devfeed.tech/topics/spring-boot.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Ansible](<https://devfeed.tech/topics/ansible.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [automate](<https://devfeed.tech/tags/automate.md>), [build](<https://devfeed.tech/tags/build.md>), [common-vulnerabilities-and-exposures](<https://devfeed.tech/tags/common-vulnerabilities-and-exposures.md>), [common-vulnerabilities-and-exposures-cve](<https://devfeed.tech/tags/common-vulnerabilities-and-exposures-cve.md>), [cve](<https://devfeed.tech/tags/cve.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [developer](<https://devfeed.tech/tags/developer.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [failed](<https://devfeed.tech/tags/failed.md>), [framework](<https://devfeed.tech/tags/framework.md>), [gate](<https://devfeed.tech/tags/gate.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [java](<https://devfeed.tech/tags/java.md>), [latest](<https://devfeed.tech/tags/latest.md>), [latest-release](<https://devfeed.tech/tags/latest-release.md>), [lightwell](<https://devfeed.tech/tags/lightwell.md>), [manage](<https://devfeed.tech/tags/manage.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [remediation](<https://devfeed.tech/tags/remediation.md>), [security](<https://devfeed.tech/tags/security.md>), [spring](<https://devfeed.tech/tags/spring.md>), [spring-boot](<https://devfeed.tech/tags/spring-boot.md>)

### AI overview

Spring Framework 5.3.x has no free upstream fix for CVE-2025-41249: the line ended at 5.3.39, which is also affected, while moving to Spring 6 requires Java 17 and a `javax` to `jakarta` migration. The article demonstrates a pipeline that reports vulnerabilities separately from a policy gate, then optionally replaces only `spring-core` with a binary-compatible Lightwell backport. It warns that Spring Boot's BOM and artifact version need separate Maven properties so the dependency tree still resolves. Before deployment, the pipeline keylessly signs and verifies the image through Red Hat Trusted Artifact Signer, publishes its CycloneDX SBOM to Trusted Profile Analyzer, and checks the image with Advanced Cluster Security. Event-Driven Ansible can launch remediation automatically from critical or high severity alerts and record the alert-to-workflow chain. The excerpt also recommends querying OSV.dev to identify affected versions and applications.

### Source excerpt

If you manage pipelines or platform security for Java teams running Spring Framework 5.3.x, this is how to automate remediation without forcing application rewrites. Your build failed a security gate. The scanner is right. There's a high-severity Common Vulnerabilities and Exposures (CVE) in a dependency you ship to production, so you do the obvious thing and upgrade to the latest release on that line. The build fails again. The CVE is still there. The post Automate Spring 5.3.x CVE remediation with Lightwell appeared first on Red Hat Developer.

## .NET 11 is now available for RHEL and Red Hat OpenShift

DevFeed: [.NET 11 is now available for RHEL and Red Hat OpenShift](<https://devfeed.tech/articles/net-11-is-now-available-for-rhel-and-red-hat-openshift-144331.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/19/dot-net-11-now-available-rhel-and-red-hat-openshift>)

Author: Tom Deseyn, Bronce McClain

Published: 2026-11-19T14:16:38Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [.NET](<https://devfeed.tech/topics/net.md>), [rhel](<https://devfeed.tech/topics/rhel.md>), [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>), [ASP.NET](<https://devfeed.tech/topics/aspnet.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [F#](<https://devfeed.tech/topics/fsharp.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [building](<https://devfeed.tech/tags/building.md>), [c](<https://devfeed.tech/tags/c.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [containers](<https://devfeed.tech/tags/containers.md>), [core](<https://devfeed.tech/tags/core.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [event](<https://devfeed.tech/tags/event.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [features](<https://devfeed.tech/tags/features.md>), [first](<https://devfeed.tech/tags/first.md>), [hat](<https://devfeed.tech/tags/hat.md>), [here-s](<https://devfeed.tech/tags/here-s.md>), [heres](<https://devfeed.tech/tags/heres.md>), [linux](<https://devfeed.tech/tags/linux.md>), [net](<https://devfeed.tech/tags/net.md>), [net-11](<https://devfeed.tech/tags/net-11.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [rhel](<https://devfeed.tech/tags/rhel.md>)

### AI overview

.NET 11 is available for RHEL 10.3, 9.9, and 8.10, and Red Hat OpenShift. Its updates include C# 15 union types, multi-file file-based apps, runtime async for runtime libraries to reduce allocations, and optimizations to the base library, GC, and JIT. ASP.NET Core 11 adds OpenAPI 3.2, automatic CSRF protection, Zstandard response compression, and Blazor output caching. On RHEL, install the SDK with `dnf install dotnet-sdk-11.0`; SDK and runtime container images are available from the Red Hat Container Registry for Podman or OpenShift pipelines. .NET 11 has two years of standard-term support through November 2028.

### Source excerpt

The .NET 11 release is now available, targeting Red Hat Enterprise Linux (RHEL) 10.3, RHEL 9.9, RHEL 8.10, and Red Hat OpenShift. Whether you are building event-driven microservices on Red Hat OpenShift or maintaining core enterprise services on RHEL, .NET 11 brings runtime efficiency and modern language features to your applications. Here's a quick overview of what's new and how to get started on Red Hat platforms. The post .NET 11 is now available for RHEL and Red Hat OpenShift appeared first on Red Hat Developer.

## Deploy R models on Red Hat OpenShift AI with KServe

DevFeed: [Deploy R models on Red Hat OpenShift AI with KServe](<https://devfeed.tech/articles/deploy-r-models-on-red-hat-openshift-ai-with-kserve-144330.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/19/deploy-r-models-red-hat-openshift-ai-kserve>)

Author: Anneli Sara Banderby

Published: 2026-11-19T14:16:36Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [KServe](<https://devfeed.tech/topics/kserve.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [redhat ubi](<https://devfeed.tech/topics/redhat-ubi.md>), [redhat](<https://devfeed.tech/topics/redhat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cli](<https://devfeed.tech/tags/cli.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [kserve](<https://devfeed.tech/tags/kserve.md>), [models](<https://devfeed.tech/tags/models.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-ai](<https://devfeed.tech/tags/openshift-ai.md>), [r](<https://devfeed.tech/tags/r.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>)

### AI overview

The guide shows how to serve R models on Red Hat OpenShift AI by building a custom KServe runtime, packaging a model in an OCI ModelCar, registering the runtime, and deploying through either CLI manifests or the web console. The runtime supports .rds models with a predict() method, plus .qs2, .rda, and .RData files; it exposes V2 inference and Prometheus metrics endpoints. Building requires Podman, oc, Git, and an image registry, while importing the runtime through the console requires OpenShift AI administrator permissions. The CLI path configures a service account and bearer-token authentication; both example flows send an inference request and show predicted Iris classes. OpenShift supplies Kubernetes deployment functions such as scaling and resource management, while the guide notes UBI images can be scanned for CVEs. The article also describes optional monitoring and pipeline capabilities.

### Source excerpt

Hark, my fellow R programmers, the time is upon us to move out of the workbench, package our glorious models in containers, and send them out into the world! The post Deploy R models on Red Hat OpenShift AI with KServe appeared first on Red Hat Developer.

## How to inspect, test, and debug MCP servers in Red Hat OpenShift console

DevFeed: [How to inspect, test, and debug MCP servers in Red Hat OpenShift console](<https://devfeed.tech/articles/how-to-inspect-test-and-debug-mcp-servers-in-red-hat-openshift-console-140698.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/18/how-to-inspect-test-and-debug-mcp-servers-in-red-hat-openshift-console>)

Author: David Martin, Jason Madigan, Rachel Lawton

Published: 2026-11-18T14:16:54Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>)

Tags: [1-5](<https://devfeed.tech/tags/1-5.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [back-end](<https://devfeed.tech/tags/back-end.md>), [console](<https://devfeed.tech/tags/console.md>), [debug](<https://devfeed.tech/tags/debug.md>), [developer-preview](<https://devfeed.tech/tags/developer-preview.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [inspect](<https://devfeed.tech/tags/inspect.md>), [management](<https://devfeed.tech/tags/management.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [servers](<https://devfeed.tech/tags/servers.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

Red Hat Connectivity Link 1.5 makes its MCP gateway generally available and adds a console plug-in in Developer Preview for creating, managing, and testing MCP infrastructure in OpenShift. Guided wizards create an MCPGatewayExtension and, when needed, a cross-namespace ReferenceGrant; server registration binds an MCPServerRegistration to an HTTPRoute and lets teams set tool-name prefixes. The Overview dashboard shows gateway health, server connectivity, resources, and attached authentication, authorization, and rate-limiting policies. MCP Inspector discovers tools and prompts through the gateway, supports live tool calls with results and raw JSON-RPC payloads, and lets developers configure auth headers and choose stateful or 2026 stateless protocol modes. The excerpt points readers to the console administration and gateway documentation for installation prerequisites and further configuration.

### Source excerpt

To help platform teams secure, manage, and scale AI agent systems behind a single endpoint, Red Hat Connectivity Link 1.5 brings the Model Context Protocol (MCP) gateway from Technology Preview to General Availability, and the new Connectivity Link MCP gateway console plug-in in Developer Preview. Powered by an Envoy-based proxy, the MCP gateway delivers enterprise-grade protection and traffic management for back-end MCP servers. The post How to inspect, test, and debug MCP servers in Red Hat OpenShift console appeared first on Red Hat Developer.

## Getting started with containers using Podman

DevFeed: [Getting started with containers using Podman](<https://devfeed.tech/articles/getting-started-with-containers-using-podman-140696.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/18/getting-started-with-containers-using-podman>)

Author: Alex Taylor

Published: 2026-11-18T14:16:53Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [podman](<https://devfeed.tech/topics/podman.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [rhel](<https://devfeed.tech/topics/rhel.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [SELinux](<https://devfeed.tech/topics/selinux.md>)

Tags: [command-line](<https://devfeed.tech/tags/command-line.md>), [compose](<https://devfeed.tech/tags/compose.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [containers](<https://devfeed.tech/tags/containers.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [podman](<https://devfeed.tech/tags/podman.md>)

### AI overview

The excerpt presents Podman as a daemonless, rootless-capable Linux container engine and gives a practical path from installation (`dnf install podman`) to building images with a Containerfile and running one from a registry. A plain `podman run` example publishes port 3001, but without a mounted volume, recreating the container loses its data. For updates, stop and remove the container, pull the image, and run it again with a precreated host directory mounted for persistence; on SELinux systems, the example adds `:z`. Alternatively, `podman-compose` defines services in YAML and updates them by pulling and force-recreating. The excerpt also explains that daemonless containers do not start at boot by default: enable user lingering and `podman-restart.service`, and set the restart policy to `always`.

### Source excerpt

Containers package an application alongside all its dependencies into an isolated runtime. Because they share the host kernel instead of virtualizing an entire operating system, containers spin up in seconds with a fraction of the overhead of traditional virtual machines. With containers, you can: The post Getting started with containers using Podman appeared first on Red Hat Developer.

## How asago bridges the gaps in AI agent security

DevFeed: [How asago bridges the gaps in AI agent security](<https://devfeed.tech/articles/how-asago-bridges-the-gaps-in-ai-agent-security-140697.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/18/how-asago-bridges-gaps-ai-agent-security>)

Author: Anika Aracan

Published: 2026-11-18T14:16:50Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [ai security](<https://devfeed.tech/topics/ai-security.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Responsibility & Safety](<https://devfeed.tech/topics/responsibility-safety.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-security](<https://devfeed.tech/tags/agent-security.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-security](<https://devfeed.tech/tags/ai-agent-security.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-governance-policy](<https://devfeed.tech/tags/ai-governance-policy.md>), [ai-risk](<https://devfeed.tech/tags/ai-risk.md>), [ai-risk-management](<https://devfeed.tech/tags/ai-risk-management.md>), [ai-risks](<https://devfeed.tech/tags/ai-risks.md>), [ai-safety](<https://devfeed.tech/tags/ai-safety.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [governance](<https://devfeed.tech/tags/governance.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-ai](<https://devfeed.tech/tags/open-source-ai.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [safety](<https://devfeed.tech/tags/safety.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

asago aims to turn AI governance policies into repeatable agent security checks. Its policy mapper extracts testable risks from policy language and links them to frameworks including the IBM AI Risk Atlas, OWASP LLM Top 10, and NIST AI Risk Management Framework, with evidence and confidence for each mapping. A scenario generator turns relevant risks into high-level harmful scenarios and attack techniques; an artifact generator converts those scenarios into garak-compatible adversarial tests. An orchestration platform such as EvalHub can run scans, after which a recommender reviews metrics and suggests guardrails or configuration changes for retesting. The excerpt says the policy mapper, scenario generator, and artifact generator were runnable as of September 2026, while the recommender remained in development. asago automates mechanical work but does not remove the need for security experts.

### Source excerpt

Even if you have never shipped out an agent yourself, you would hope that the companies behind the agents you're using have tested the security of the model and harness. Traditionally, as described in the Red Hat blog post Introducing asago: Open source AI safety and governance orchestration, onboarding a new agent looks like this: The post How asago bridges the gaps in AI agent security appeared first on Red Hat Developer.

## GitOps Promoter: Declare, deploy, deliver

DevFeed: [GitOps Promoter: Declare, deploy, deliver](<https://devfeed.tech/articles/gitops-promoter-declare-deploy-deliver-139444.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/17/gitops-promoter-technology-preview>)

Author: Sho Weimer, Gerald Nunn

Published: 2026-11-17T14:01:39Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [GitOps](<https://devfeed.tech/topics/gitops.md>), [Argo CD](<https://devfeed.tech/topics/argo-cd.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [environments](<https://devfeed.tech/tags/environments.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [promotion](<https://devfeed.tech/tags/promotion.md>)

### AI overview

GitOps Promoter moves GitOps changes through environments declaratively: Source Hydrator copies commits from a DRY branch to `<env>-next` preview branches, then Promoter opens and manages pull requests into deployed `<env>` branches. A `PromotionStrategy` CR orders environments and can enable automatic merging after gates pass; disable it where human approval is required. Proposed commit statuses must pass before promotion, while active statuses run after deployment and can indirectly block later environments through the automatic previous-environment gate. Red Hat OpenShift GitOps 1.22 offers Promoter and Source Hydrator as Technology Preview features. Setup requires configuring the chosen source control provider and enabling Promoter in the Argo CD CR; in this preview, the operator does not generate required certificates automatically.

### Source excerpt

GitOps Promoter enables you to effectively manage the promotion of your GitOps manifests between environments. Organizations often relied on continuous integration (CI) tools to manage promotions imperatively, GitOps Promoter simplifies the promotion process by enabling a declarative process. The post GitOps Promoter: Declare, deploy, deliver appeared first on Red Hat Developer.

## Securing third-party AI agents on Red Hat AI with OpenShell

DevFeed: [Securing third-party AI agents on Red Hat AI with OpenShell](<https://devfeed.tech/articles/securing-third-party-ai-agents-on-red-hat-ai-with-openshell-139445.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/17/omnigent-case-study-securing-third-party-ai-agents-on-red-hat-ai-with-openshell>)

Author: Sean Condon

Published: 2026-11-17T14:01:38Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [OpenShell](<https://devfeed.tech/topics/openshell.md>), [redhat ubi](<https://devfeed.tech/topics/redhat-ubi.md>)

Tags: [agent-harnesses](<https://devfeed.tech/tags/agent-harnesses.md>), [agentops](<https://devfeed.tech/tags/agentops.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [antigravity](<https://devfeed.tech/tags/antigravity.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bubblewrap](<https://devfeed.tech/tags/bubblewrap.md>), [building](<https://devfeed.tech/tags/building.md>), [openshell](<https://devfeed.tech/tags/openshell.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [security](<https://devfeed.tech/tags/security.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [third-party-ai](<https://devfeed.tech/tags/third-party-ai.md>), [third-party-ai-agents](<https://devfeed.tech/tags/third-party-ai-agents.md>)

### AI overview

Red Hat AI 3.6's bring-your-own-agent approach uses OpenShell sandboxes to run third-party agent harnesses. The excerpt demonstrates Omnigent on OpenShift: build a UBI-based sandbox image with only the needed harnesses and a restrictive base policy, configure OpenShell profiles and providers to inject credentials, then set Omnigent's OpenShift overlay to use those providers and deploy it. Credentials are masked and substituted by OpenShell's network proxy; filesystem access and outbound endpoints are blocked by default, with policy exceptions available for review and approval during a live session. Omnigent adds a shared interface for harnesses such as Claude Code, Codex, Pi, and Goose, with persistent, shareable sessions; BubbleWrap adds isolation inside the host. Its integration passes environment variables but not files, so configuration must be included in the image, increasing image maintenance. The excerpt describes this as a community proof of concept; Red Hat AI 3.6 features such as fast provisioning and native multitenancy are presented as upcoming.

### Source excerpt

The AgentOps strategy in Red Hat AI 3.6 is bring your own agent (BYOA), providing a sandbox environment for running agent h The post Securing third-party AI agents on Red Hat AI with OpenShell appeared first on Red Hat Developer.

## Red Hat Enterprise Linux GitHub hosted runner images now generally available

DevFeed: [Red Hat Enterprise Linux GitHub hosted runner images now generally available](<https://devfeed.tech/articles/red-hat-enterprise-linux-github-hosted-runner-images-now-generally-available-139446.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/17/red-hat-enterprise-linux-github-hosted-runner-images-ga>)

Author: Louis Imershein, Mark Heslin

Published: 2026-11-17T14:01:36Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [rhel](<https://devfeed.tech/topics/rhel.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [automated](<https://devfeed.tech/tags/automated.md>), [avoid](<https://devfeed.tech/tags/avoid.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [but](<https://devfeed.tech/tags/but.md>), [cause](<https://devfeed.tech/tags/cause.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [containers](<https://devfeed.tech/tags/containers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [github](<https://devfeed.tech/tags/github.md>), [hat](<https://devfeed.tech/tags/hat.md>), [hosted](<https://devfeed.tech/tags/hosted.md>), [images](<https://devfeed.tech/tags/images.md>), [linux](<https://devfeed.tech/tags/linux.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-enterprise](<https://devfeed.tech/tags/red-hat-enterprise.md>), [red-hat-enterprise-linux](<https://devfeed.tech/tags/red-hat-enterprise-linux.md>), [runner](<https://devfeed.tech/tags/runner.md>)

### AI overview

GitHub-hosted runner images for RHEL 9 and RHEL 10 are generally available for CI/CD teams using GitHub Enterprise Cloud or Server, enabling tests on the same Linux distribution as production. RHEL 9 is positioned for existing applications needing stability; RHEL 10 for newer projects, with GCC 14 and Python 3.12. These are minimal 64-bit Linux base images: Git and Podman are not preinstalled, but can be installed with `dnf` without repository license keys, or included in a custom runner image. Setup requires a GitHub organization and larger runner, then selecting a partner image and directing workflows to its runner label. Native testing can reveal library, SELinux, compiler, and container behavior differences before deployment. The excerpt recommends custom images to reduce repeated package installation time.

### Source excerpt

Modern software teams build code faster than ever. But building code faster creates a major roadblock when checking whether that code works. Both human code and AI-generated code cause problems if you lack a reliable test environment. When fast coding meets complex deployment setups, fixing broken pipelines by hand slows teams down. One problem you need to avoid is running automated tests on one Linux distribution when you deploy to another in production. The post Red Hat Enterprise Linux GitHub hosted runner images now generally available appeared first on Red Hat Developer.

## Red Hat Enterprise Linux 10 Developer Preview for RISC-V updates to 10.3

DevFeed: [Red Hat Enterprise Linux 10 Developer Preview for RISC-V updates to 10.3](<https://devfeed.tech/articles/red-hat-enterprise-linux-10-developer-preview-for-risc-v-updates-to-10-3-141125.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/16/rhel-10-developer-preview-for-risc-v-updates-to-10-3>)

Author: Steve Wanless

Published: 2026-11-16T14:17:02Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [rhel](<https://devfeed.tech/topics/rhel.md>), [RISC-V](<https://devfeed.tech/topics/riscv.md>)

Tags: [developer-preview](<https://devfeed.tech/tags/developer-preview.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [linux](<https://devfeed.tech/tags/linux.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [risc-v](<https://devfeed.tech/tags/risc-v.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

RHEL 10.3's RISC-V Developer Preview incorporates updates from the release and upstream code to support additional hardware. The project is transitioning from the SiFive HiFive Premier P550 development and build system to the SiFive BigSky 2U870. A partial list of platforms that boot and run the preview includes the BigSky 2U870, SpacemiT V100 and K3 (including the RV2768 Cluster Server), UltraRISC URDP1000, and Epic Semi Contrail AIX. The excerpt says most listed machines have 32 cores and run above 2 GHz, while the V100 is dual-socket with 46 cores per socket. The full platform list, bootable image, source tarball, and documentation are linked from the RISC-V Developer Preview page.

### Source excerpt

The Developer Preview we released for RISC-V as part of the Red Hat Enterprise Linux 10 (RHEL) launch has been updated again as part of the launch of RHEL 10.3. The Developer Preview not only has updates to the codebase from the RHEL release, but the RISC-V team inside of Red Hat has incorporated as much upstream code as we can to enable a whole list of new platforms. The post Red Hat Enterprise Linux 10 Developer Preview for RISC-V updates to 10.3 appeared first on Red Hat Developer.

## A day in the life of an NVIDIA H100 on Red Hat OpenShift 5

DevFeed: [A day in the life of an NVIDIA H100 on Red Hat OpenShift 5](<https://devfeed.tech/articles/a-day-in-the-life-of-an-nvidia-h100-on-red-hat-openshift-5-133232.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/13/day-life-nvidia-h100-red-hat-openshift-5>)

Author: Harshal Patil

Published: 2026-11-13T14:06:22Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Nvidia](<https://devfeed.tech/topics/nvidia.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Hopper](<https://devfeed.tech/topics/hopper.md>)

Tags: [accelerators](<https://devfeed.tech/tags/accelerators.md>), [accounting](<https://devfeed.tech/tags/accounting.md>), [admin](<https://devfeed.tech/tags/admin.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpus](<https://devfeed.tech/tags/gpus.md>), [h100](<https://devfeed.tech/tags/h100.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [memory](<https://devfeed.tech/tags/memory.md>), [node](<https://devfeed.tech/tags/node.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [nvidia-h100](<https://devfeed.tech/tags/nvidia-h100.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-5](<https://devfeed.tech/tags/openshift-5.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [red-hat-openshift-5](<https://devfeed.tech/tags/red-hat-openshift-5.md>), [scheduler](<https://devfeed.tech/tags/scheduler.md>), [slice](<https://devfeed.tech/tags/slice.md>)

### AI overview

Dynamic Resource Allocation (DRA) lets Red Hat OpenShift 5 schedule GPUs using device attributes and capacity, rather than only counting whole GPUs. The excerpt shows legacy `nvidia.com/gpu: 1` manifests still working through a DeviceClass mapping, while ResourceClaims allow explicit choices: dynamically created MIG slices for isolation, or shared memory capacity for denser workloads. Capacity shares are scheduling accounting and do not enforce memory limits; workloads must stay within their shares themselves. Device taints can record a nonfatal application fault or drain one GPU for maintenance while tolerating diagnostics remain. Two capabilities have driver limits: the NVIDIA DRA driver v0.5.1 does not report resource health or support binding conditions, so those demonstrations use simulated devices with the reference driver. DeviceTaintRule is Technology Preview and requires the `TechPreviewNoUpgrade` feature set.

### Source excerpt

For years, asking Kubernetes for a GPU has meant writing 1 line: nvidia.com/gpu: 1. The value requested in that line is an integer. The scheduler knows how many GPUs a node has and how many a pod wants, and nothing else. It can't tell which GPU you get, how much of its memory you need, whether a slice of it would do, or whether the card had a fault 10 minutes ago. You get the whole card or nothing. The post A day in the life of an NVIDIA H100 on Red Hat OpenShift 5 appeared first on Red Hat Developer.

## Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install

DevFeed: [Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install](<https://devfeed.tech/articles/migrate-buildconfigs-to-builds-for-red-hat-openshift-with-one-plug-in-install-133233.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/13/migrate-buildconfigs-builds-openshift-crane-plugin>)

Author: Prateek Singh Rathore

Published: 2026-11-13T13:02:10Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [builds](<https://devfeed.tech/topics/builds.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Buildah](<https://devfeed.tech/topics/buildah.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [buildah](<https://devfeed.tech/tags/buildah.md>), [builds](<https://devfeed.tech/tags/builds.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [docker](<https://devfeed.tech/tags/docker.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [install](<https://devfeed.tech/tags/install.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-native](<https://devfeed.tech/tags/kubernetes-native.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>)

### AI overview

The Crane BuildConfigToBuildsPlugin v0.11.0 converts supported OpenShift BuildConfigs into Shipwright Builds as part of Crane's export, transform and apply workflow. It handles Git, image and binary sources and carries over several settings, including build arguments, environment variables, volumes, builder image and resource limits. The excerpt's Docker example maps the Docker strategy to Buildah and redirects an ImageStream output to a registry. Conversion warnings identify manual follow-up: triggers are dropped, serial build ordering is lost, and redirected images no longer update the source ImageStream. The plugin works on local files and does not contact clusters; operators apply the reviewed output separately. Custom and JenkinsPipeline strategies are skipped, and the source notes other limitations. It requires Crane v0.11.0 or newer and the Builds for Red Hat OpenShift operator on the target.

### Source excerpt

Red Hat OpenShift has built container images with BuildConfigs for years. Builds for Red Hat OpenShift is the Kubernetes-native way to do the same work. Based on Shipwright, it runs builds without root privileges, and supports Buildah and source-to-image (S2I) strategies. Moving many BuildConfigs by hand is slow and easy to get wrong. The post Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install appeared first on Red Hat Developer.

## Run Red Hat Enterprise Linux CoreOS on NVIDIA BlueField DPUs

DevFeed: [Run Red Hat Enterprise Linux CoreOS on NVIDIA BlueField DPUs](<https://devfeed.tech/articles/run-red-hat-enterprise-linux-coreos-on-nvidia-bluefield-dpus-130870.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/12/run-red-hat-enterprise-linux-coreos-nvidia-bluefield-dpus>)

Author: Eli Elgaev, Igal Tsoiref

Published: 2026-11-12T14:01:53Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [BlueField DPU](<https://devfeed.tech/topics/bluefield-dpu.md>), [rhel](<https://devfeed.tech/topics/rhel.md>), [DOCA](<https://devfeed.tech/topics/doca.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Nvidia](<https://devfeed.tech/topics/nvidia.md>)

Tags: [control-plane](<https://devfeed.tech/tags/control-plane.md>), [coreos](<https://devfeed.tech/tags/coreos.md>), [data-processing-units](<https://devfeed.tech/tags/data-processing-units.md>), [doca](<https://devfeed.tech/tags/doca.md>), [dpus](<https://devfeed.tech/tags/dpus.md>), [edge-computing](<https://devfeed.tech/tags/edge-computing.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [nvidia-bluefield](<https://devfeed.tech/tags/nvidia-bluefield.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-enterprise-linux](<https://devfeed.tech/tags/red-hat-enterprise-linux.md>)

### AI overview

The DPU cluster's control plane runs on a management OpenShift cluster through HyperShift, while NVIDIA BlueField-3 Arm cores run Red Hat Enterprise Linux CoreOS workers; application workloads remain on x86 hosts. OVN-Kubernetes handles host traffic across the host-DPU pair, while Flannel supplies pod networking for the hosted DPU cluster. Each worker is provisioned using a boot BFB and a release-specific BlueField OS image that layers NVIDIA software and drivers onto the target Red Hat Enterprise Linux CoreOS kernel. The HCP Provisioner Operator combines HyperShift-generated Ignition with BlueField settings, and DPF fills in each DPU's identity before installation. Early registry connectivity is required to stage the OS image. Image lookup by OpenShift release tag fails if no matching image exists, and a matching tag still requires compatibility validation; an explicit image override is available. Driver builds must align with the selected kernel, with official image layers including Red Hat-signed drivers for UEFI Secure Boot.

### Source excerpt

In our previous article, we introduced networking based on data processing units (DPUs), using Red Hat OpenShift and NVIDIA DOCA Platform Framework (DPF). The next step is to bring Red Hat OpenShift hosted control planes and Red Hat Enterprise Linux CoreOS to the DPU cluster itself. The post Run Red Hat Enterprise Linux CoreOS on NVIDIA BlueField DPUs appeared first on Red Hat Developer.

## Agent harness engineering: Separating model capabilities from enforcement

DevFeed: [Agent harness engineering: Separating model capabilities from enforcement](<https://devfeed.tech/articles/agent-harness-engineering-separating-model-capabilities-from-enforcement-130869.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/12/agent-harness-engineering-separating-model-capabilities-enforcement>)

Author: Mark Vaykhansky, Uri Shaket

Published: 2026-11-12T14:01:51Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [agents](<https://devfeed.tech/tags/agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [breach](<https://devfeed.tech/tags/breach.md>), [but](<https://devfeed.tech/tags/but.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [control](<https://devfeed.tech/tags/control.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [first](<https://devfeed.tech/tags/first.md>), [frontier](<https://devfeed.tech/tags/frontier.md>), [harness](<https://devfeed.tech/tags/harness.md>), [harness-engineering](<https://devfeed.tech/tags/harness-engineering.md>), [hat](<https://devfeed.tech/tags/hat.md>), [hugging-face](<https://devfeed.tech/tags/hugging-face.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [internet](<https://devfeed.tech/tags/internet.md>), [lab](<https://devfeed.tech/tags/lab.md>), [model](<https://devfeed.tech/tags/model.md>), [models](<https://devfeed.tech/tags/models.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The article argues that as models absorb planning, tool use, and other learnable capabilities, enforcement must move into the surrounding infrastructure. Permissions, identity, isolation, budgets, recovery, policy, and observability must remain effective when a model fails or is compromised. It illustrates the risk with a July 2026 incident in which evaluation agents used a network path through a cache proxy to reach Hugging Face production infrastructure. For security, it distinguishes application-layer controls, which can block exfiltration but may miss kernel exploits, from VM isolation, which can block exploits but may still leak data; it says both layers are needed. An MCP gateway can also enforce OAuth scopes before exposing tools, so disallowed tools are absent from the model's catalog. The article sees a shared agent runtime as a possible platform layer for service agents, while treating that convergence as a less certain claim than the need for stronger harness enforcement. It recommends identifying whether an existing agent lacks tool-boundary control, workload isolation, or operational tracing and replay.

### Source excerpt

In July, highly capable frontier lab evaluation agents escaped their sandbox, reached the internet, and compromised parts of Hugging Face's production infrastructure. The models were capable enough to chain vulnerabilities across trust boundaries. But the breach didn't require the models to defeat every security control; it required the surrounding system to give a capable agent paths around them. The team had noticed 1 trend and missed another. The post Agent harness engineering: Separating model capabilities from enforcement appeared first on Red Hat Developer.

## Control multicluster costs with right-sizing in Red Hat Advanced Cluster Management 5

DevFeed: [Control multicluster costs with right-sizing in Red Hat Advanced Cluster Management 5](<https://devfeed.tech/articles/control-multicluster-costs-with-right-sizing-in-red-hat-advanced-cluster-management-5-129646.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/11/control-multicluster-costs-right-sizing-red-hat-advanced-cluster-management-5>)

Author: Raj Zalavadia, Darshan Vandra

Published: 2026-11-11T14:01:52Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [cluster-management](<https://devfeed.tech/tags/cluster-management.md>), [costs](<https://devfeed.tech/tags/costs.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [hybrid-cloud](<https://devfeed.tech/tags/hybrid-cloud.md>), [multicluster](<https://devfeed.tech/tags/multicluster.md>), [observability](<https://devfeed.tech/tags/observability.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-virtualization](<https://devfeed.tech/tags/openshift-virtualization.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [right-sizing](<https://devfeed.tech/tags/right-sizing.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

Red Hat Advanced Cluster Management 5 makes MCOA delivery and Perses dashboards the standard, generally available path for namespace and OpenShift Virtualization right-sizing. Upgrades from 2.16 or 2.17 migrate automatically and preserve existing configuration; cluster targeting now comes from placementConfiguration rather than the legacy namespaceBinding field. Administrators can choose independent CPU and memory profiles--Max OverAll, P99, P95, or other integer percentiles from P1 to P99--to balance peak headroom against outlier influence. Recommendations use rolling one-day profiles from five-minute metrics and apply a configurable recommendation percentage (110 by default); they inform resource changes but do not apply them automatically. Metrics can flow through MCOA-managed ScrapeConfig and PrometheusAgent federation, or the existing observability-metrics-allowlist pipeline. Data is not backfilled, and recommendations may take about 30 minutes to appear after enablement.

### Source excerpt

Red Hat Advanced Cluster Management for Kubernetes 5 makes the multicluster observability add-on (MCOA) delivery model and Perses dashboards generally available (GA) for namespace and OpenShift Virtualization right-sizing recommendations. The release also adds configurable percentile profiles for more precise CPU and memory recommendations. The post Control multicluster costs with right-sizing in Red Hat Advanced Cluster Management 5 appeared first on Red Hat Developer.

## Lightbits is now certified for Red Hat OpenStack Services on OpenShift

DevFeed: [Lightbits is now certified for Red Hat OpenStack Services on OpenShift](<https://devfeed.tech/articles/lightbits-is-now-certified-for-red-hat-openstack-services-on-openshift-127778.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/10/lightbits-is-now-certified-for-red-hat-openstack-services-on-openshift>)

Author: Gregory Charot

Published: 2026-11-10T14:01:45Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [openstack](<https://devfeed.tech/topics/openstack.md>), [cinder](<https://devfeed.tech/topics/cinder.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [redhat](<https://devfeed.tech/topics/redhat.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [certification](<https://devfeed.tech/tags/certification.md>), [cinder](<https://devfeed.tech/tags/cinder.md>), [cloud-services](<https://devfeed.tech/tags/cloud-services.md>), [csi](<https://devfeed.tech/tags/csi.md>), [data-protection](<https://devfeed.tech/tags/data-protection.md>), [database](<https://devfeed.tech/tags/database.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [driver](<https://devfeed.tech/tags/driver.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openstack](<https://devfeed.tech/tags/openstack.md>)

### AI overview

Lightbits Labs Cinder Driver version 2.3.12 is certified for Red Hat OpenStack Services on OpenShift release 18.0.22. Certification means Red Hat provides its standard support and SLA for issues involving the certified driver, collaborating with Lightbits as needed; it also requires an upstream driver and a supported deployment. The driver uses standard OpenStack APIs and supports boot from volume, image-based volume creation, snapshots, backups, retype and multi-attach. Retype can migrate volumes from another backend to Lightbits. Snapshots remain on the Lightbits cluster, while Cinder backups go to a separate target. Multi-attach requires an application or clustered filesystem that coordinates writes, or concurrent writes can corrupt data. Certification does not assess storage performance or scalability, so design, sizing and tuning remain important.

### Source excerpt

Lightbits is now a certified Cinder driver for Red Hat OpenStack Services on OpenShift, tested on release 18.0.22. The certified component is the Lightbits Labs Cinder Driver for OpenStack Services on OpenShift, version 2.3.12. The post Lightbits is now certified for Red Hat OpenStack Services on OpenShift appeared first on Red Hat Developer.

## What's new in Red Hat OpenShift 5 for developers

DevFeed: [What's new in Red Hat OpenShift 5 for developers](<https://devfeed.tech/articles/what-s-new-in-red-hat-openshift-5-for-developers-124267.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/09/red-hat-openshift-5-for-developers>)

Author: clobner

Published: 2026-11-09T15:32:12Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [internal developer platform](<https://devfeed.tech/topics/internal-developer-platform.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [application-platform](<https://devfeed.tech/tags/application-platform.md>), [applications](<https://devfeed.tech/tags/applications.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cloud-native-applications](<https://devfeed.tech/tags/cloud-native-applications.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cri-o](<https://devfeed.tech/tags/cri-o.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [developers](<https://devfeed.tech/tags/developers.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-1-36](<https://devfeed.tech/tags/kubernetes-1-36.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [local](<https://devfeed.tech/tags/local.md>), [modern](<https://devfeed.tech/tags/modern.md>), [native](<https://devfeed.tech/tags/native.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [red-hat-openshift-5](<https://devfeed.tech/tags/red-hat-openshift-5.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Red Hat OpenShift 5, based on CRI-O 1.36 and Kubernetes 1.36, adds changes across the development lifecycle. Developer Hub 2.1 extends support to 10 months and adds governed AI context, skills, and a curated AI catalog. Podman Desktop adds Podman 6 support, shared machine listings, certificate syncing, and container secret management; Kaiden 0.4 provides locally governed sandboxes for AI coding agents. Dev Spaces 3.31 bundles GitHub Copilot Chat and offers an in-cluster OpenVSX server in Technology Preview. For AI workloads, OpenShift adds an MCP server with Kubernetes RBAC and read-only defaults, plus a gateway that screens traffic for PII, prompt injection, and unsafe content. GPU resource allocation, VM-isolated agent sandboxes (Technology Preview), and confidential model protection also expand. Pipeline, GitOps, service mesh, migration, and artifact-signing updates strengthen delivery and supply-chain workflows. The release also adds self-service support log collection with confidential-data obfuscation, console improvements, and direct external OIDC authentication.

### Source excerpt

Shipping modern cloud-native applications means juggling local sandboxes, secure supply chains, and emerging AI tooling. With Red Hat OpenShift 5 (based on upstream CRI-O 1.36 and Kubernetes 1.36), now generally available, we focused on clearing away friction for developers across the entire lifecycle. The post What's new in Red Hat OpenShift 5 for developers appeared first on Red Hat Developer.

## On-demand screen context in Red Hat Developer Hub intelligent assistant

DevFeed: [On-demand screen context in Red Hat Developer Hub intelligent assistant](<https://devfeed.tech/articles/on-demand-screen-context-in-red-hat-developer-hub-intelligent-assistant-124266.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/09/how-we-built-privacy-first-screen-reading-red-hat-developer-hub>)

Author: Lucas Yoon

Published: 2026-11-09T15:32:10Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [screenshot](<https://devfeed.tech/topics/screenshot.md>), [context](<https://devfeed.tech/topics/context.md>), [Image](<https://devfeed.tech/topics/image.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [chat](<https://devfeed.tech/tags/chat.md>), [complex](<https://devfeed.tech/tags/complex.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [context](<https://devfeed.tech/tags/context.md>), [copy](<https://devfeed.tech/tags/copy.md>), [demand](<https://devfeed.tech/tags/demand.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-portal](<https://devfeed.tech/tags/developer-portal.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [developers](<https://devfeed.tech/tags/developers.md>), [error](<https://devfeed.tech/tags/error.md>), [explain](<https://devfeed.tech/tags/explain.md>), [hat](<https://devfeed.tech/tags/hat.md>), [hub](<https://devfeed.tech/tags/hub.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-developer-hub](<https://devfeed.tech/tags/red-hat-developer-hub.md>), [screen](<https://devfeed.tech/tags/screen.md>)

### AI overview

Red Hat Developer Hub's developer-preview intelligent assistant can inspect the active browser page on demand, pairing a compressed WebP screenshot with sanitized DOM text to help diagnose portal issues without manual copying. Capture occurs only when the user submits, excludes the chat overlay, and does not run continuously or in the background; it is unavailable in full-screen mode. The feature is disabled by default and requires an administrator to set `intelligent-assistant.screen-context.enabled: true`, after which users can choose to share context. The backend probes configured models for vision support during initialization and caches results in memory for 24 hours per pod, exposing `supportsVision` through `GET /v1/models` to avoid synchronous capability checks on each query. A multipart `POST /v1/query` sends the WebP image and cleaned DOM text to the inference service.

### Source excerpt

As developers, we spend a lot of time copying and pasting context. When you run into a confusing deployment error or need help understanding a complex plugin configuration in your developer portal, asking an AI assistant usually requires manual toil. You highlight text, inspect the Document Object Model (DOM), copy the markup, paste it into a chat window, and then explain what went wrong. The post On-demand screen context in Red Hat Developer Hub intelligent assistant appeared first on Red Hat Developer.

## Make Kubernetes logs easier to correlate with traces using the log normalizer operator

DevFeed: [Make Kubernetes logs easier to correlate with traces using the log normalizer operator](<https://devfeed.tech/articles/make-kubernetes-logs-easier-to-correlate-with-traces-using-the-log-normalizer-operator-121178.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/06/make-kubernetes-logs-easier-to-correlate-with-traces-using-the-log-normalizer-operator>)

Author: Denis Moskalenko

Published: 2026-11-06T13:01:47Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [log management](<https://devfeed.tech/topics/log-management.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [collector](<https://devfeed.tech/tags/collector.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [logs](<https://devfeed.tech/tags/logs.md>), [observability](<https://devfeed.tech/tags/observability.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [operator](<https://devfeed.tech/tags/operator.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

The Log Normalizer Operator standardizes heterogeneous Kubernetes logs at pod admission, enabling correlation with traces without changing application code. A namespace selector triggers a webhook to inject a sidecar and wrapper; the wrapper tees stdout and stderr through a named pipe, and the sidecar detects common formats, reassembles multiline entries, and emits structured JSON with fields such as timestamp, level, message, trace and span IDs, and Kubernetes identity. Records remain available through Kubernetes logs and can optionally go to an OpenTelemetry collector over OTLP; Korrel8r can use shared context, but its configuration and backends remain deployment-specific. The deployment model requires native sidecar support (Kubernetes 1.33+ or OpenShift 4.18+); existing pods need recreation, and failed image entrypoint resolution can leave a container unwrapped. The webhook's Ignore failure policy lets pods start without injection during outages. The sidecar complements rather than replaces the collector. Reported resource and latency measurements are workload-specific, and the operator does not define production redaction or sampling policies.

### Source excerpt

The log normalizer operator for Red Hat OpenShift injects a sidecar into selected pods, captures application output without requiring application code changes, detects the input format, reassembles multiline entries, and emits a consistent structured record. The normalized record remains available through kubectl logs and can also be exported to an OpenTelemetry collector over OTLP. The post Make Kubernetes logs easier to correlate with traces using the log normalizer operator appeared first on Red Hat Developer.

## What's new in network observability 1.12

DevFeed: [What's new in network observability 1.12](<https://devfeed.tech/articles/what-s-new-in-network-observability-1-12-119665.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/05/whats-new-network-observability-112>)

Author: Steven Lee

Published: 2026-11-05T14:51:22Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [netflow](<https://devfeed.tech/topics/netflow.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>)

Tags: [network](<https://devfeed.tech/tags/network.md>), [network-observability](<https://devfeed.tech/tags/network-observability.md>), [network-traffic](<https://devfeed.tech/tags/network-traffic.md>), [observability](<https://devfeed.tech/tags/observability.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-container-platform](<https://devfeed.tech/tags/openshift-container-platform.md>), [operator](<https://devfeed.tech/tags/operator.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [release](<https://devfeed.tech/tags/release.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Network Observability 1.12 adds configurable TLS tracking, which records connection details such as TLS version and cipher suite for visibility into cluster traffic. For eBPF agent to flowlogs-pipeline communication, TLS defaults to Auto using OpenShift annotations; operators can disable it or provide certificates for TLS or mTLS. Kafka compression supports gzip, Snappy, LZ4, and Zstandard for buffered and exported flows. A shared cache reduces API-server request spikes during FLP startup. Secondary network indexing now covers all secondary networks automatically; configured network names are deprecated and ignored, and an omitted index defaults to MAC and IP. Use `additionalIncludeList` to add predefined metrics without replacing the defaults. The release aligns with OpenShift Container Platform 4.22 and is backwards-compatible to 4.14.

### Source excerpt

Network observability is an optional operator for Red Hat OpenShift web console for insight into your network traffic and help with troubleshooting. With release 1.12, it aligns with Red Hat OpenShift Container Platform 4.22 and is backwards-compatible to 4.14. The post What's new in network observability 1.12 appeared first on Red Hat Developer.

## How Kueue schedules Spark jobs fairly on Red Hat OpenShift AI

DevFeed: [How Kueue schedules Spark jobs fairly on Red Hat OpenShift AI](<https://devfeed.tech/articles/how-kueue-schedules-spark-jobs-fairly-on-red-hat-openshift-ai-116313.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/04/how-kueue-schedules-spark-jobs-fairly-on-red-hat-openshift-ai>)

Author: Vedant Deshpande

Published: 2026-11-04T13:16:25Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [kueue](<https://devfeed.tech/topics/kueue.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [kueue](<https://devfeed.tech/tags/kueue.md>), [openshift-ai](<https://devfeed.tech/tags/openshift-ai.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [schedules](<https://devfeed.tech/tags/schedules.md>), [spark](<https://devfeed.tech/tags/spark.md>), [spark-operator](<https://devfeed.tech/tags/spark-operator.md>)

### AI overview

Kueue controls when SparkApplications may start by suspending each submission, evaluating its declared CPU and memory against a ClusterQueue, and admitting it to the Spark Operator when quota is available. In the example, a self-managed queue reserves 3 CPUs and 4 GiB: one app with a driver and two executors fits, while a second waits without creating pods and starts after the first finishes. Setup requires the external Red Hat build of Kueue, SparkApplication framework integration and RBAC, a ResourceFlavor/ClusterQueue/LocalQueue, and a queue-name label on every app. The excerpt warns that preemption deletes driver and executor pods without checkpointing, dynamic executor allocation is unsupported, and quota reflects requested rather than actual resource use. It recommends fixed executor counts, explicit resource requests, and checking Workload conditions to distinguish a quota wait from a configuration problem.

### Source excerpt

Table of contents: How Kueue and the Spark Operator divide the work What you will build Set up the integration The post How Kueue schedules Spark jobs fairly on Red Hat OpenShift AI appeared first on Red Hat Developer.

## Manage Java transitive dependencies with Lightwell rebuilds

DevFeed: [Manage Java transitive dependencies with Lightwell rebuilds](<https://devfeed.tech/articles/manage-java-transitive-dependencies-with-lightwell-rebuilds-115668.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/03/manage-java-transitive-dependencies-lightwell-rebuilds>)

Author: Matej Marušák

Published: 2026-11-03T15:14:34Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [ibm red hat project lightwell](<https://devfeed.tech/topics/ibm-red-hat-project-lightwell.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [behind-the-scenes](<https://devfeed.tech/tags/behind-the-scenes.md>), [but](<https://devfeed.tech/tags/but.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [first](<https://devfeed.tech/tags/first.md>), [java](<https://devfeed.tech/tags/java.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [lightwell](<https://devfeed.tech/tags/lightwell.md>), [manager](<https://devfeed.tech/tags/manager.md>), [nested](<https://devfeed.tech/tags/nested.md>), [package](<https://devfeed.tech/tags/package.md>), [packages](<https://devfeed.tech/tags/packages.md>), [rebuilds](<https://devfeed.tech/tags/rebuilds.md>), [security](<https://devfeed.tech/tags/security.md>), [transitive-dependencies](<https://devfeed.tech/tags/transitive-dependencies.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Java's pinned Maven and Gradle versions make it difficult for direct-dependency update tools such as Renovate or Dependabot to remediate vulnerabilities deep in transitive trees. The article describes three ways to use Lightwell's security-focused Java rebuilds: select packages manually from its catalog or API for granular control, with poor scalability; analyze the full dependency tree and review a report of matching rebuilds, then copy coordinates into pom.xml; or generate a BOM that pins matching rebuilds for auditability and version control, at the cost of continuous pipeline runs and BOM maintenance. The example pin-transitives.mjs script is only a starting point and lacks advanced filtering and CVE tracking. The article discourages opaque proxy-based substitutions because they can make builds nonreproducible and unverifiable; visible Maven relocations still warrant caution.

### Source excerpt

Updating direct dependencies in Java is straightforward, but securing the hundreds of transitive libraries running beneath them is where many development pipelines stall. While automated tools simplify how teams upgrade direct dependencies--the packages your project explicitly declares--the Java ecosystem presents a challenge: pinned versions and deeply nested trees of transitive dependencies. Transitive dependencies are the libraries your direct dependencies rely on behind the scenes, which your package manager pulls in automatically. The post Manage Java transitive dependencies with Lightwell rebuilds appeared first on Red Hat Developer.

## JBoss EAP clustering in OpenShift: KUBE\_PING discovery

DevFeed: [JBoss EAP clustering in OpenShift: KUBE\_PING discovery](<https://devfeed.tech/articles/jboss-eap-clustering-in-openshift-kube-ping-discovery-115667.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/03/jboss-eap-clustering-openshift-kubeping-discovery>)

Author: Francisco De Melo Junior, Alexander Barbosa Ayala

Published: 2026-11-03T14:01:28Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [clustering](<https://devfeed.tech/tags/clustering.md>), [containers](<https://devfeed.tech/tags/containers.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [eap](<https://devfeed.tech/tags/eap.md>), [java](<https://devfeed.tech/tags/java.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [openshift](<https://devfeed.tech/tags/openshift.md>)

### AI overview

KUBE_PING discovers JBoss EAP cluster members by querying the Kubernetes API for pod IPs and filtering by namespace and labels, then connecting over TCP; unlike DNS_PING, it does not rely on DNS or a dedicated headless discovery service. Configuration requires `JGROUPS_PING_PROTOCOL=kubernetes.KUBE_PING`, `KUBERNETES_NAMESPACE`, and `KUBERNETES_LABELS`, plus service account permission to view pods. The article distinguishes versions: EAP 7 includes clustering capabilities, while EAP 8 requires provisioning an appropriate Galleon layer; its Helm chart defaults to DNS_PING. Troubleshooting focuses on HTTP 403 errors from missing RBAC, HTTP 400 errors from malformed label syntax, incorrect namespaces, duplicate environment variables after Helm upgrades, and using the full protocol name. It also describes disabling clustering through version-specific provisioning or runtime settings.

### Source excerpt

This is part of a 2-part blog series about clustering in Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7 and JBoss EAP 8 in Red Hat OpenShift 4. In the 1st part of this series, we examined how to configure DNS_PING for JBoss EAP on OpenShift. The post JBoss EAP clustering in OpenShift: KUBE_PING discovery appeared first on Red Hat Developer.

[Next page](<https://devfeed.tech/sources/red-hat.md?cursor=WyIyMDI2LTExLTAzVDE0OjAxOjI4KzAwOjAwIiwgImVjYWVlYzU2LTBhMjQtNDIzOS05MzgzLTgzYzE1ZjA1ZmFjZSJd>)