RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2161712 - allow container networking configuration
Summary: allow container networking configuration
Keywords:
Status: CLOSED ERRATA
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-11-07 09:30 UTC (History)
8 users (show)

Fixed In Version: rhel-system-roles-1.22.0-0.16.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2220963 (view as bug list)
Environment:
Last Closed: 2023-11-07 08:29:32 UTC
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
Red Hat Product Errata RHEA-2023:6390 0 None None None 2023-11-07 08:30:02 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!

Comment 19 errata-xmlrpc 2023-11-07 08:29:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:6390


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