-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Static IP with "podman play kube --network=<network> --ip=<IP>" #8442
Comments
Interested in opening a PR to add this functionality? |
@rhatdan: Oh i think my knowledge about go and the code is not good enough for it :) |
Ok no problem, I just thought I would ask. |
@rhatdan i would like to take this as my "first issue" |
Thanks @mier85, you got it. |
A friendly reminder that this issue had no activity for 30 days. |
@hoonetorg as you requested this feature, there is some question about it here: #8617 (comment) |
A friendly reminder that this issue had no activity for 30 days. |
@mier85 What is the scoop on this one? |
A friendly reminder that this issue had no activity for 30 days. |
@umohnani8 PTAL |
A friendly reminder that this issue had no activity for 30 days. |
@Luap99 any chance you could look at this? |
Sure |
PR #10043 |
Add a new --ip flag to podman play kube. This is used to specify a static IP address which should be used for the pod. This option can be specified several times because play kube can create more than one pod. Fixes containers#8442 Signed-off-by: Paul Holzinger <[email protected]>
Add a new --ip flag to podman play kube. This is used to specify a static IP address which should be used for the pod. This option can be specified several times because play kube can create more than one pod. Fixes containers#8442 Signed-off-by: Paul Holzinger <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
It would be useful if
podman play kube
would support using static IP for the generated pod.The usecase for me is a dhcphelper pod which uses the host network wants to talk to a app pod, which has dnsmasq running in it. Forwarding DHCP requests from dhcphelper pod to app pod with dnsmasq container is easy by using a static IP.
Steps to reproduce the issue:
podman play kube app.yaml --network=app --ip=192.168.2.253
Describe the results you received:
Error: unknown flag: --ip
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
virtual
The text was updated successfully, but these errors were encountered: