Bug 1861760

Summary: RFE: podman - join multiple CNI network and set static IPs for them (multiple static networks)
Product: Red Hat Enterprise Linux 8 Reporter: Markus Schibli <mschibli>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Joy Pu <ypu>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: bbaude, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, tsweeney, ypu
Target Milestone: rcKeywords: FutureFeature
Target Release: 8.6   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: podman-4.0.0-0.25.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 13:27:31 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1186913    

Description Markus Schibli 2020-07-29 13:50:03 UTC
1. Proposed title of this feature request
podman - join multiple CNI network and set static IPs for them

2. Who is the customer behind the request?
see private comment

3. What is the nature and description of the request?
With podman-1.9.3-2.module+el8.2.1+6867+366c07d6 which we ship with RHEL 8.2.1 , customer is able to join one ( 1 ) CNI network and can configure a static IP. In the future they need to configure multiple static networks on their podman containers. Today it is not possible/supported.

4. Why does the customer need this? (List the business requirements here)
In the future they need to configure multiple static networks on their podman containers.

5. How would the customer like to achieve this? (List the functional requirements here)
for example:
# podman run -d --rm --name instance0 --network mynetwork1 --ip 172.25.0.200 --network mynetwork2 --ip 192.168.0.200 image:version

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
When "mynetwork1+ and "mynetwork2" are up and are able to communicate over these two networks

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
no

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
RHEL8

9. Is the sales team involved in this request and do they have any additional input?
no

10. List any affected packages or components.
podman-1.9.3-2

11. Would the customer be able to assist in testing this functionality if implemented?
yes

Comment 6 Daniel Walsh 2020-09-11 20:24:04 UTC
We should look at this for RHEL8.4 release.

Comment 9 Daniel Walsh 2021-01-28 11:53:17 UTC
Matt how close to we come to this now?

Comment 10 Matthew Heon 2021-01-28 14:18:24 UTC
CNI presently only allows one static IP to be set, total. We can join multiple networks, or set a static IP, but not both. The good news is that I'm fairly certain the fix for this is in OCICNI, which we have much more control over than the actual CNI plugins. Probably not terrible to handle, but I haven't looked too deeply - if we do need CNI plugins changes the scale of the fix will rapidly increase.

Comment 11 Daniel Walsh 2021-06-11 14:25:22 UTC
Is this something we can address with the redesign?

Comment 12 Matthew Heon 2021-06-11 14:29:40 UTC
Yes

Comment 13 Markus Schibli 2021-11-19 13:00:51 UTC
Hi,
customer would like to have an update on this bz. Do you have any ETA when it could be fixed and in which version? Thanks a lot.

Comment 14 Matthew Heon 2021-11-19 14:29:41 UTC
Target is Podman 4.0, set to release RHEL 8.6.0. A reworking of the Podman network stack to enable features like this is presently under heavy development.

Comment 17 Tom Sweeney 2022-01-20 22:34:42 UTC
This will be contained in Podman v4.0.0-RC2, currently scheduled for delivery today or tomorrow dependent upon the CI gods.
@jnovy I'm setting this to Post and assigning to you for any further BZ and Packaging needs.

Comment 30 errata-xmlrpc 2022-05-10 13:27:31 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 (Important: container-tools:rhel8 security, 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/RHSA-2022:1762