ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Automate RHEL setups with subscription‑manager: register, attach pools, enable repos, and install packages in one idempotent script. Learn trade‑offs, limitations, and how to integrate this into CI/CD pipelines.
Create a reproducible Execution Environment image with your own collections, push it to Automation Hub, and attach it to a job template. Follow this step‑by‑step guide to keep playbooks consistent across teams.
RHEL 9 ships with systemd‑resolved, a DNS stub resolver that adds caching and DNSSEC. This blog walks through enabling it, configuring Cloudflare’s DNSSEC‑enabled servers, and verifying cache hits while highlighting migration trade‑offs.
Learn how Red Enterprise Linux’s kpatch lets you apply critical kernel patches in memory, avoiding reboots. Follow a step‑by‑step example, weigh trade‑offs, and discover best‑practice monitoring.
Decide whether to use RHEL's traditional dnf-managed package mode or the newer image mode (bootc/OCI). Compare mutability, update model, tooling, and fleet fit, then walk through a minimal build-and-deploy test.
New RHEL deployments can run in classic package mode or image mode (bootc). This guide compares both supported models, their trade-offs, and a concrete VM validation cycle.
RHEL 9 lets you declare Podman containers in systemd‑style .container files, called Quadlets. These files are turned into systemd services at daemon‑reload time, giving you a vendor‑supported, declarative alternative to docker‑compose or hand‑written unit files.
Deploy Red Hat OpenShift Service Mesh using sidecar injection to secure, observe, and make microservices resilient. This architecture note covers requirements, design, trust boundaries, operational checks, failure modes, and when to change the design.
Goal Expose a container service on a host port 80 while running Podman in rootless mode on RHEL. Current Constraints Rootless containers run in a user namespace; kernel capability checks still apply. The boundary is defined by net.ipv4.ip_unprivileged_port_start (1024 by default). The value cannot be overridden per container. Podman’s --privileged flag in ro
redhat
ansible
podman