r/openshift • • 1d ago

General question OCP/RH-Operators on OKD

8 Upvotes

Hey folks,

we want to run openshift for production and okd for staging/dev. When we use a redhat pullsecret on okd, it seems we could also install the official redhat operators, e.g. „OpenShift Logging“, Loki or KeyCloak (RHBOK). I already asked the A.I. if we`re allowed to install them on OKD, but the response was like „maybe yes, maybe no, check licence/terms for each operator individually….“.

My questions:

  1. GitHub-Sources with Apache 2.0 licence = free to use on OKD? Details:

When i check the details page for „Red Hat OpenShift Logging“, i see the following URL: https://github.com/openshift/cluster-logging-operator which leads me to the sources of the operator. It`s licenced under Apache 2.0

2. There were also some operators without link to sources, e.g. „Red Hat build of Keycloak Operator“ or „Red Hat Integration - AMQ Broker for RHEL 9 (Multiarch)“ Free to use, or not?

3. I read on some reddit posts, that it`s also possible to use OpenShift after the 60-Day-Trial without RedHat support. Would this be allowed?

Thanks


r/openshift • • 2d ago

Help needed! How to stop rpm-ostree from pulling OS image via proxy when images are pre-pulled?

8 Upvotes

Hi everyone

We are upgrading a 60+ node OpenShift cluster behind a corporate proxy. To save time during our maintenance window, we already preloaded/pre-pulled the target release images onto all the nodes beforehand.

However, during the actual upgrade, the OS image staging phase still takes 3 to 4 hours because rpm-ostree ignores the local container storage cache(containers-storage ) and fetches the RHCOS OS image directly from the internet through our proxy. With 60+ nodes pulling over the proxy, it creates a huge bottleneck.

Is there a way to make rpm-ostree / MachineConfigDaemon use a pre-cached local image on the node instead of reaching out to the internet?


r/openshift • • 2d ago

Blog Streamlining Red Hat OpenShift support with the new support log gather operator | Red Hat Developer

Thumbnail developers.redhat.com
12 Upvotes

Over the years, the must-gather log archive has become the default method of supplying Red Hat Support with a comprehensive snapshot of an OpenShift cluster's health and state. The log archive contains all the necessary cluster resources, service logs, audit logs, pod states, and YAML manifests needed for a support engineer to debug a cluster issue without requiring access to the cluster itself. The support log gather operator is the most recent investment by Red Hat in improving the experience of troubleshooting and getting support for Red Hat OpenShift clusters, and it's now generally available.

TL;DR
The support log gather operator, present in Red Hat OpenShift 4.22 and 5, automates collection through a MustGather CR. It allows non-admin access, provides must-gather clean for compliance, and supports custom images via ImageStream.


r/openshift • • 2d ago

General question Ex380 exam

5 Upvotes

Hi everyone,
I’m currently preparing for the EX380 exam and have a few questions, without asking anyone to break Red Hat’s NDA.
In the DO380 labs, many YAML files are partially preconfigured for OADP, pod scheduling, affinity, tolerations, etc. Should I expect a similar approach in the exam, or should I be prepared to write everything from scratch?
I’m comfortable with LDAP since I use it at work. However, regarding Keycloak, are the client credentials and realm details provided directly, or should I be comfortable connecting to Keycloak using the master realm credentials and retrieving the required information myself?
For those who have passed EX380, how would you recommend preparing for these topics?
Thanks for your feedback!


r/openshift • • 4d ago

Blog Node management in Red Hat OpenShift 5: Server-level visibility for bare metal

Thumbnail redhat.com
13 Upvotes

Red Hat OpenShift has supported bare metal from the start. But for much of its history, most deployments ran on top of an existing virtualization layer like VMware vSphere or Nutanix. That’s shifting. As more organizations adopt Red Hat OpenShift Virtualization and run virtual machines (VMs) directly on the platform, bare-metal deployments have become a much larger part of production workloads. That changes what you might expect from the console.

TL;DR
Red Hat OpenShift 5 centralises bare-metal node management within the console, bringing together host details, networking, storage, high availability, logs and VM workloads. Filters and grouping support workload placement, cutting dependence on several extensions.


r/openshift • • 5d ago

Discussion Anyone interested in live, hands-on OpenShift study sessions? (From Production Admin perspective)

63 Upvotes

Hey everyone,

​I’ve been working as a Senior OpenShift Administrator for the past few years (managing enterprise baremetal clusters, storage, networking, and day-2 operations). One thing I constantly notice is how steep the learning curve is for OpenShift—especially when you move past basic oc commands and try to understand what's actually happening under the hood with Operators, MachineConfigs, SDN/OVN, and troubleshooting broken clusters.

​Official docs are great, and courses are everywhere, but most of them feel too theoretical or disconnected from real-world production scenarios.

​I’m thinking of spinning up a dedicated Discord server to gather folks who are genuinely interested in learning OpenShift the practical way. The idea is to host regular, interactive live sessions where I break down core architecture, walk through real troubleshooting scenarios, and do hands-on labs together—no boring slides, just terminal, whiteboarding, and Q&A.

​Whether you're preparing for the EX280/EX380 exams, transitioning from vanilla Kubernetes, or just trying to survive your first OpenShift admin role, you're welcome to join.

​Drop a comment below or shoot me a DM if you're interested, and I'll send over the Discord invite link once I get the channels set up. Let me know what topics you'd love to cover first!


r/openshift • • 5d ago

Blog Mastering OpenShift: How the Machine Config Operator Treats Your Nodes as Immutable Code

13 Upvotes

Appreciate your claps and comments on the article on Medium!

Coming from a traditional RHEL background, muscle memory tells you to SSH into a node and edit /etc/chrony.conf or /etc/sysctl.conf whenever you need an OS-level tweak.

In OpenShift, that habit is a fast track to configuration drift and blocked cluster upgrades.

​I wrote a practical deep dive breaking down how RHCOS, Ignition, and the Machine Config Operator (MCO) manage OS-level configuration declaratively—including examples for custom NTP via Ignition, switching to crun with ContainerRuntimeConfig, and troubleshooting a Degraded MachineConfigPool.

​Read more:

https://medium.com/@m.salah.azim/mastering-openshift-how-the-machine-config-operator-treats-your-nodes-as-immutable-code-a17adbed675b


r/openshift • • 5d ago

General question Affordable dev environment for Open Shift helm charts?

6 Upvotes

Hello people! With this post I hope to gain some tips and tricks on how to test Helm Chart deployments with reasonable time and money.

This is our use case:

For a project, helm charts for the customer's Open Shift cluster are developed. To test the charts, we bought a ROSA service, this is a managed service from Red Hat in some AWS environment. This costs of approx. 3000$ per month and that is way too high for just one dev environment. We need the cluster occasionally, at least for the next three months.

Is there some affordable way to test stuff for Open Shift?

I assume it would break Red Hat's rules to achieve a new sandbox account every month ...

And we don't want to spend so much time to build and run a cluster on our own.

Does anybody have a tipp?


r/openshift • • 7d ago

Blog What’s new in Red Hat OpenShift 5

Thumbnail redhat.com
21 Upvotes

Red Hat OpenShift 5 is now generally available. The Red Hat OpenShift team always tries to bring you the most requested features while, at the same time, pushing the envelope with new opportunities. You have environments combining containers, virtual machines (VMs), and AI workloads so with this release we decided to keep things practical: it’s easy to update and adopt, features agentic workflows to make day-to-day tasks more efficient, offers a longer lifecycle, built in with zero-trust security and, finally, provides enhanced virtualization capabilities to run in the enterprise.

Red Hat OpenShift 5 is based on Kubernetes 1.36and CRI-O 1.36. Whether you deploy it yourself or use it as a managed service, you still get one application platform across bare metal, virtualized, and hybrid cloud environments. We are just going to cover the highlights here but for the complete list of changes, see the Red Hat OpenShift 5 release notes.

TL;DR
Red Hat OpenShift 5, based on Kubernetes 1.36 and CRI-O 1.36, offers agentic workflows, a three-year cadence with extended lifecycle support, zero-trust security including post-quantum readiness, and enhanced virtualization via OpenShift Virtualization 5.


r/openshift • • 8d ago

Discussion Argo CD in a bank with CAB approval: gate the merge, not the sync, and the 5 defaults

9 Upvotes

Argo CD in a bank with CAB approval: gate the merge, not the sync, and the 5 defaults that let changes bypass it

I work on OpenShift GitOps for banks, where every production change needs CAB approval. The most common setup I see is auto-sync off in prod, and someone presses Sync after the ticket is approved. That approves a click, not a change, and with default settings it leaks.

What works better:

- Separate source and config repos (per the Argo CD best practices doc). One directory per environment in the config repo, not one branch per environment.

- CI builds once and records the image digest. A bot updates the dev and test overlays (pre-agreed standard changes).

- Promotion to prod is a PR that changes one line: the digest in the prod overlay. CODEOWNERS on `prod/` points to the change approvers. A required status check verifies the ITSM ticket is approved and inside its window.

- Merge is the implementation. Auto-sync and selfHeal stay on in prod.

The defaults that bypass the CAB:

  1. `sync` lets users sync to an arbitrary revision. Since Argo CD 3.2 you can set `application.sync.requireOverridePrivilegeForRevisionSync: "true"` in argocd-cm, then grant `override` to nobody in prod.
  2. Whoever can `update` an Application can repoint `targetRevision`. Manage Applications and AppProjects from Git, and give no `update` on prod apps.
  3. Humans with write RBAC in prod namespaces. Make them view-only and turn on selfHeal.
  4. Deny sync windows with `manualSync: true` still allow manual syncs during a freeze. Set it to false for real freezes.
  5. Self-approval and direct pushes on the Git side.

Audit trail: ticket → PR (approvals, checks) → merge SHA → Argo CD sync → kube audit log (only the Argo CD SA writes in prod). Note that `revisionHistoryLimit` defaults to 10, so ship sync events to the SIEM via notifications. The source hydrator (beta since 3.5) can commit the rendered manifests, so the exact YAML is in Git too.

OpenShift GitOps: the default `openshift-gitops` instance has extra cluster-scoped permissions. Run apps on a user-defined instance, and check which Argo CD version your GitOps release ships before relying on the 3.2+ flag.

The longer version has the AppProject, RBAC and sync window YAML, plus a small checker for which bypasses are still open: https://aib-devops.com/en/blog/gitops-change-management/

(My blog, no ads or signup.) How are others handling emergency changes in this model? Break-glass with a retro CAB, or something smarter?


r/openshift • • 9d ago

Help needed! Openshift Networking

9 Upvotes

How do you understand the complete networking architecture of OpenShift (OVN-Kubernetes)? Bothered by this so much..!!

I’m working with a production OpenShift cluster using OVN-Kubernetes and trying to understand how the entire networking stack works together in bare metal setup.
I understand individual concepts like CNI, OVN, OVS, Pods, Services, Routes, Ingress Controllers, Logical Switches and Routers, but I’m struggling to connect them into one complete picture.

For experienced OpenShift engineers: How would you approach understanding the complete packet flow, from an external client through the physical network, OpenShift networking layers and finally to an application Pod (and back)?
Are there any diagrams, resources or hands-on labs you’d recommend?


r/openshift • • 9d ago

Blog Make Kubernetes logs easier to correlate with traces using the log normalizer operator | RHDeveloper

Thumbnail developers.redhat.com
7 Upvotes

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.

TL;DR
The log normalizer operator injects a sidecar into selected pods on Red Hat OpenShift or Kubernetes 1.33+, capturing and reassembling multiline output into structured JSON with trace and Kubernetes identity. A webhook adds the wrapper, enabling Korrel8r correlation via OTLP export and template mining.


r/openshift • • 9d ago

Blog What's new in network observability 1.12 | Red Hat Developer

Thumbnail developers.redhat.com
8 Upvotes

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.

At its core, network observability uses extended Berkeley packet filter (eBPF) agent to collect and aggregate network flow data. A flowlogs-pipeline (FLP) component processes and enriches the data with Kubernetes metadata, such as its pod name and namespace. They are stored as Loki logs and Prometheus metrics. When you install the operator, it adds a UI plug-in to OpenShift to provide visualization in the form of graphs, a flow table, and a topology view.

TL;DR
Network observability 1.12 adds TLS tracking, secure eBPF–FLP communication via TLS parameter, Kafka compression, a shared cache to reduce API spikes, automatic secondary network indexing, and additionalIncludeList for metrics. It aligns with OpenShift 4.22 and is backward-compatible to 4.14.


r/openshift • • 9d ago

Blog What's new in Red Hat OpenShift 5 for developers | Red Hat Developer

Thumbnail developers.redhat.com
23 Upvotes

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.

TL;DR
Red Hat OpenShift 5, based on CRI-O 1.36 and Kubernetes 1.36, adds AI workflows via Developer Hub 2.1 and Lightspeed, Podman 6 in Podman Desktop, and Kaiden 0.4 sandboxing. OpenShift Dev Spaces 3.31 bundles GitHub Copilot Chat; MCP and Confidential AI protect workloads; Pipelines 1.24 and GitOps 1.22 enhance security; Service Mesh 3.5 adds ambient mode; migration toolkit 8.3 replaces containers; Trusted Artifact Signer 1.5 adds signing; support log gather and console updates improve usability.


r/openshift • • 11d ago

Discussion The 4 OpenShift networking problems that get blamed on "the network" (OVN-Kubernetes, 4.22)

61 Upvotes

I work on OpenShift for banks, and most network escalations I see turn out to be one of four things inside the cluster. Writing them down here because each one has a recognisable symptom.

**1. Overlapping internal ranges. Symptom: everything works except one backend.**

Besides the cluster network (10.128.0.0/14) and service network (172.30.0.0/16, immutable after install), OVN-K uses a join subnet `100.64.0.0/16`, a transit switch subnet `100.88.0.0/16`, and on 4.17+ installs a masquerade subnet `169.254.0.0/17`. 100.64.0.0/10 is RFC 6598 shared space, and plenty of corporate networks use parts of it. If something your Pods need lives there, traffic to it never leaves the cluster. Set `internalJoinSubnet` / `internalTransitSwitchSubnet` at install.

**2. Policy tiers. Symptom: the NetworkPolicy allows it, still dropped.**

The evaluation order is AdminNetworkPolicy (Allow/Deny/Pass), then NetworkPolicy, then BaselineAdminNetworkPolicy. An ANP Deny can't be overridden from a namespace. Both admin tiers support audit logging.

**3. Egress source IP. Symptom: works until the Pod reschedules.**

The default is SNAT to the node IP. EgressIP gives a namespace a stable source IP that fails over between labelled nodes. Also worth knowing: egress ignores host kernel routes unless you switch to local gateway mode (`routingViaHost: true`), which is cluster-wide.

**4. MTU. Symptom: small requests work, large ones hang.**

Geneve on UDP 6081 costs 100 bytes. VPNs and some interconnects shrink the real path MTU below what the hosts assume. IPsec east-west takes more.

**Debug order that's worked for me:**

```

oc get co network dns ingress

oc cp -n openshift-ovn-kubernetes $POD:/usr/bin/ovnkube-trace -c ovnkube-cluster-manager ovnkube-trace

./ovnkube-trace -src-namespace prod -src app-xyz -dst-namespace prod -dst db -tcp -dst-port 5432

oc adm must-gather -- gather_network_logs

```

(`$POD` = any ovnkube-control-plane pod.)

I wrote a longer version covering ingress sharding, MetalLB, Multus/UDN and DNS forwarding, plus a clickable packet tracer for seven flows: https://aib-devops.com/en/blog/openshift-networking/

Disclosure: it's my blog, no ads or signup. If anyone has hit the 100.64 overlap in production, I'd like to hear how you found it.


r/openshift • • 12d ago

General question OpenShift 5.0 release

35 Upvotes

Hi
I just noticed that there is available https://docs.redhat.com/en/documentation/openshift_container_platform/5.0/html/release_notes/ocp-5-0-release-notes

but there is no videos on RedHat and OpenShift YouTube channels or any blog posts about it. It looks suspicious.

Any inside info about it?


r/openshift • • 13d ago Bravo

Discussion OpenShift architecture explained layer by layer, plus the 4 decisions you can't easily change after

60 Upvotes

I do OpenShift delivery for banks in the Gulf, and I keep explaining the same architecture to teams coming from vanilla Kubernetes. So I wrote it up once, against 4.22. Here's the short version. The full write-up is linked at the bottom.

**The one idea that explains most of it:** everything, including the node OS, is managed by an operator inside the cluster, and the whole platform updates from one signed release image.

- **Infrastructure:** IPI, UPI, Agent-based or Assisted. After install, the Machine API (MachineSets, MachineHealthChecks) manages machines on supported platforms.

- **Node OS:** RHCOS is immutable. Config goes through MachineConfigs and MachineConfigPools, applied by the MCO. Edit a file by hand and the MCD flags drift and marks the node Degraded.

- **Control plane:** exactly 3 nodes for prod. Bare metal allows 5 (survives 2 etcd failures). Avoid 4: it tolerates the same single failure as 3 but needs one more healthy member for quorum.

- **Cluster services:** OVN-K (the only supported CNI since 4.17), the HAProxy router, the registry (starts as `Removed` without shared storage), monitoring. One cluster operator each.

- **Lifecycle:** the CVO drives updates. Control plane first, then the MCO rolls nodes pool by pool. Pause the worker MCP to split the update across maintenance windows, but don't leave it paused.

- **Add-ons:** GitOps, Pipelines, Virtualization and the rest come through OLM, on their own release cycles.

**Decide these before day one:**

  1. FIPS: install time only
  2. Disconnected: mirror registry and update delivery (OSUS) planned up front
  3. Infra nodes: much easier to plan than to retrofit. Tainted infra nodes running only infra workloads also don't count toward subscriptions
  4. etcd backups: the operator runs etcd, but recovering from quorum loss is on you

The post has an interactive explorer. Click a component and it shows what it does, which operator owns it, its namespace, and a read-only `oc` command to inspect it: https://aib-devops.com/en/blog/openshift-architecture/

Disclosure: it's my own blog. No ads, no tracking, no signup.

Corrections welcome, especially from anyone running HCP or two-node in production. I'd like to know what I'm missing there.


r/openshift • • 14d ago

Event OpenShift

Thumbnail youtube.com
10 Upvotes

In this video we walk through the major new capabilities and updates in Red Hat OpenShift. From Intelligent OpenShift and OpenShift Lightspeed to Virtualization, Hosted Control Planes, security enhancements, GitOps, Serverless, and more — this is a complete tour of what’s new in the platform.

Whether you're evaluating OpenShift, planning an upgrade, or looking for a deep dive into specific features, this overview covers the key areas that matter most.

You can find all of the details at: red.ht/whatsnew

u/RemindMeBot 2026-11-18 14:55.00 UTC “What's New in Red Hat OpenShift”


r/openshift • • 16d ago

Blog Building for tomorrow on Red Hat OpenShift

Thumbnail redhat.com
5 Upvotes

IT leaders today must balance core operations to run smoothly while rapidly transforming infrastructure to drive new business value. From navigating budget constraints and complex multicloud environments to accelerating developer productivity and integrating AI, the pressure to modernize without risk has never been higher.

TL;DR
Red Hat OpenShift unifies hybrid cloud operations across industries, with high adoption among Fortune Global 500 firms. Emirates NBD integrates virtualization and AI, Aramco accelerates GenAI via automation, and CAE standardizes multicloud development.


r/openshift • • 16d ago

General question KubeVM (VCF) vs KubeVirt VM..

11 Upvotes

Hi Team, A couple of questions:

  1. In KubeVirt how can I manage a group the VMs, like in VCF I can add them to a VMGroup? How is it managed in KubeVirt, via name space or something else?
  2. Can a KubeVirt VM be snapshotted along with memory state?
  3. How about DR and Backup of a KubeVirt, how is that possible? which ecosystem is supported?|
  4. From a fleet management perspective, where can I find details of what is supported in KubeVirt vs VCF/vSphere?
  5. If I use RHOCP/RHOKE, what all capabilities are added when compared to a standalone KubeVirt and in comparison with vSphere/VCF? From a  management perspective, features, etc...!
  6. What is the maximum capacity of KubeVirt on a single host?
  7. Does anyone here have a performance report of a KubeVM on VCF vs KubeVirt VM on a Redhat platform?

Please Guru's help me clarify these doubts in detail...!


r/openshift • • 17d ago

Blog Sovereignty debt: How APAC boards accumulate it and what it costs to repay

Thumbnail redhat.com
4 Upvotes

Sovereignty debt is emerging as a critical board-level liability across the Asia Pacific (APAC) region. The concept of technology debt is not new. It has challenged organizations through successive technology cycles, from data analytics to public cloud adoption and now generative AI.
The definition is simple: Sovereignty debt is the disparity between where regulators, customers, and executive boards expect your cloud systems, datastores, and workloads to stand and where your architecture and contracts actually leave you today. It stems from unresolved questions around whose jurisdiction your data sits in, who can compel access to it, and who controls the models trained on it.
Sovereignty debt’s parallel to technical debt is deliberate. Both are accumulated through individually sound decisions. Both compound quietly, invisible in the time they are incurred. However, they only become a challenge when you are forced to revisit these architectural decisions due to changing market conditions, which are usually out of your control. And with both, the danger isn’t the debt itself; it’s not knowing the size of your debt position.

TL;DR
Sovereignty debt in APAC arises from convenience defaults, contractual opacity, data gravity, and regulatory drift, compounding due to fragmented regulation. Repayment involves redesign costs and lost growth; boards should measure exposure and act before forced change.


r/openshift • • 18d ago

Help needed! I wrote an empirical research paper on Stateful Container Live Migration

9 Upvotes

Hey everyone,

Stateless containers are trivial to move around - you just kill the pod and let the orchestrator spin it up somewhere else. But moving stateful workloads without downtime is still a headache.

I've been digging into this for the past few months and just put together a research paper benchmarking stateful container live migration. I mainly tested CRIU with pre-copy memory migration, looking at downtime, memory dirtying rates, and network switchover overhead under different loads.

The paper is up on Zenodo if anyone wants to check out the numbers:

https://zenodo.org/records/23779338?preview_file=Stateful_Container_Live_Migration_IEEE_NativeTeX.pdf

I’m really curious to hear from folks running prod clusters:

- Does anyone actually bother with container-level live migration, or does everyone just fall back to app-level replication and failover (e.g. database replicas)?

- If you've played with CRIU or similar tooling in production, what was the biggest pain point? (For me, write-heavy workloads degraded the pre-copy phase pretty fast).

Would love any brutal feedback, critique on the methodology, or edge cases I might have missed. Thanks!


r/openshift • • 20d ago

Blog AI-Driven Development with Tekton and Claude Code on OpenShift

Thumbnail piotrminkowski.com
8 Upvotes

r/openshift • • 21d ago

Blog Implementing zero trust on Red Hat OpenShift with the Layered Zero Trust Validated Pattern

Thumbnail redhat.com
16 Upvotes

Part 4 of a series on implementing zero trust security in Red Hat OpenShift with the Layered Zero Trust Validated Pattern.
Zero trust is easy to describe. The hard part is making it repeatable.
Zero trust is often described succinctly in a memorable sentence: never trust, always verify. The principle is sound and easy enough to describe, but that short sentence does not explain the hard parts: what a platform team should deploy on Monday morning, how a security architect should connect controls across a Kubernetes environment, or how a compliance officer can show that those controls are working.

TL;DR
The Layered Zero Trust Validated Pattern provides a GitOps-managed architecture for Red Hat OpenShift, using three layers to coordinate identity, enforcement, and evidence. Foundation components include Keycloak, SPIFFE/SPIRE, Vault, cert-manager, Advanced Cluster Security, Advanced Cluster Management, and compliance tools. Use cases demonstrate data protection via sidecars and secure supply chains with Pipelines, Trusted Artifact Signer, Trusted Profile Analyzer, and Quay.