Bug 2161712 - allow container networking configuration
Summary: allow container networking configuration
Keywords:
Status: VERIFIED
Alias: None
Deadline: 2023-08-07
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.3
Assignee: Rich Megginson
QA Contact: Jakub Haruda
URL:
Whiteboard: role:podman
Depends On:
Blocks: 2220963
TreeView+ depends on / blocked
 
Reported: 2023-01-17 17:08 UTC by Rich Megginson
Modified: 2023-08-07 13:33 UTC (History)
7 users (show)

Fixed In Version: rhel-system-roles-1.22.0-0.16.el9
Doc Type: Enhancement
Doc Text:
Feature: Add support for quadlets. User can pass in quadlet units using `podman_quadlet_units`. Add support for secrets. User can pass in Ansible Vault encrypted secrets using `podman_secrets`. Reason: quadlets are the new way to implement applications in podman that use systemd services. quadlets allow you to specify everything you need to run your application - containers, services, volumes, networks, and more - using simple, systemd style unit files. Secrets such as passwords, tokens, keys, etc. are an important part of application configuration, so the role now allows those to be specified. Result: Users can deploy entire, complex applications using the podman system role using quadlet units.
Clone Of:
: 2220963 (view as bug list)
Environment:
Last Closed:
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles podman issues 42 0 None open Feature request: Podman network support 2023-01-17 18:04:06 UTC
Github linux-system-roles podman pull 78 0 None open feat: add support for quadlet, secrets 2023-06-29 01:20:02 UTC
Red Hat Issue Tracker RHELPLAN-145397 0 None None None 2023-01-17 17:09:18 UTC

Description Rich Megginson 2023-01-17 17:08:00 UTC
from https://github.com/linux-system-roles/podman/issues/42 there is no way to configure which network to run the pods on. My problem is that dns resolution between pods doesn't work for me on RHEL 8.6 and podman 4.2. It does work on Fedora 37 which has podman 4.3 which adds a default podman-kube network but I still can not add any custom networks using this role

Comment 2 Rich Megginson 2023-06-22 21:54:41 UTC
@

Comment 3 Rich Megginson 2023-06-22 21:56:50 UTC
@bblasco I have a wip of the podman role with support for quadlet, including networking and healthcheck (if using podman 4.5 or later).  https://github.com/richm/linux-system-roles-podman/tree/quadlet
It also contains an implementation of the quadlet-demo https://github.com/ygalblum/quadlet-demo, except using the podman role instead.  I would appreciate it if you could take a look at it and give it a try.

Comment 4 Benjamin Blasco 2023-06-26 01:02:57 UTC
@rmeggins I will test and share the git repo with my work with you once I have some results!


Note You need to log in before you can comment on or make changes to this bug.