SUSE and Red Hat Leftovers

posted by Roy Schestowitz on Jun 17, 2023

• The brains behind the books: Amrita Sakthivel

  This article is part of a series of articles focusing on SUSE Documentation and the minds that create the manuals, guides, quick starts, best practices and many more helpful documents.

• Harnessing the Power of Kubernetes-native API Management with Traefik Hub and Rancher Prime

  As digital transformation accelerates at an unprecedented pace, several design patterns and architectural choices have emerged to keep up with the rapid change.

• How to use Ansible to create a VM on Azure [Ed: Red Hat keeps promoting Microsoft's proprietary spyware instead of competing against that]

• Jonathan Dowland: containers as first-class network citizens

  I've moved to having containers be first-class citizens on my home network, so any local machine (laptop, phone,tablet) can communicate directly with them all, but they're not (by default) exposed to the wider Internet. Here's why, and how.

  After I moved containers from docker to Podman and systemd, it became much more convenient to run web apps on my home server, but the default approach to networking (each container gets an address on a private network between the host server and containers) meant tedious work (maintaining and reconfiguring a HTTP reverse proxy) to make them reachable by other devices. A more attractive arrangement would be if each container received an IP from the range used by my home LAN, and were automatically addressable from any device on it.