news
Fedora and Red Hat Leftovers
-
FOSSLinux ☛ Fedora CoreOS Explained: Beginner Guide to Container OS
Fedora CoreOS is an automatically updating, immutable operating system built for containers. This beginner guide covers Ignition provisioning, automatic atomic updates via Zincati, why oomd is disabled, and when CoreOS beats regular Fedora.
-
Red Hat ☛ MiDojo: Improve Hey Hi (AI) agent security with real-world red-teaming [Ed: Mostly slop promotion from IBM's Red Hat these days]
The "bring your own agent" (BYOA) approach lets you build with your preferred framework while relying on Red Hat AI for enterprise identity, isolation, guardrails, and observability—a model we recently detailed in our BYOA operationalization guide.
But there's a question before any agent should touch production data: will this agent do something unintended when someone attacks it? Not the model—the agent. The whole system of model, tools, and data working together.
-
Red Hat Official ☛ The hidden complexity of AI inference systems
Inference, by contrast, appears deceptively simple. Once a model's been trained, the assumption is serving predictions should be straightforward: load the model, send requests to it, and return results. In reality, production inference systems are among one of the most complex distributed systems to operate reliably at scale.
-
Red Hat Official ☛ Beyond the hypervisor: How a service provider migrated thousands of workloads to a unified application platform
Similar to how many are responding in the face of this virtualization disruption, Abacus took the opportunity to build a modern, unified hybrid cloud foundation. Featured technologies included Red Hat OpenShift Virtualization, Red Hat Advanced Cluster Management for Virtualization, Red Hat Ansible Automation Platform, and the migration toolkit for virtualization.
-
Red Hat ☛ Harden local container base images in Podman Desktop
Containers changed how software gets built. Build once, run anywhere, ship faster, scale farther. That part worked. The problem is what comes with the image: pull a base container and you're not just getting a runtime, you're inheriting a full package tree you didn't choose, don't need, and won't maintain when a Common Vulnerabilities and Exposure (CVE) drops. That's the supply chain problem, and it's not abstract. The gap it creates is real: what builds clean on your laptop hits a wall at the platform gate. Not because your code is wrong. Because no one built the container for production.
-
Red Hat ☛ Just-in-time access to HashiCorp Vault using the Red Hat Ansible Automation Platform OIDC provider
Centralized secrets management platforms, like HashiCorp Vault, enable organizations to protect some of their most sensitive values (think passwords, tokens, or any type of content that may be deemed protected). Red Hat Ansible Automation Platform includes integrations for several popular secrets management platforms, including HashiCorp Vault, to enable accessing secure values during automation execution. However, regardless of how secure a secrets management system is along with how it protects the content it stores, one of the biggest challenges that organizations need to contend with is handling how consumers access the secrets management platform—also known as the "secret zero problem". A breach of a long-lived credential that's used to read a range of content from the secrets management system has a potential blast radius to negatively impact the security posture of an organization.