diff options
| author | Paul Holzinger <pholzing@redhat.com> | 2022-09-29 16:59:35 +0200 |
|---|---|---|
| committer | Paul Holzinger <pholzing@redhat.com> | 2022-09-29 18:07:41 +0200 |
| commit | fe2b4df382a66889931a0158fc77d3235e00d8b8 (patch) | |
| tree | 0b6293977bdf563ba67dcb17198d4003ea8e66d6 /pkg/domain/infra | |
| parent | 4c39b391036c8383825b76ad0e2edf1efb53b4da (diff) | |
| download | podman-fe2b4df382a66889931a0158fc77d3235e00d8b8.tar.gz podman-fe2b4df382a66889931a0158fc77d3235e00d8b8.tar.bz2 podman-fe2b4df382a66889931a0158fc77d3235e00d8b8.zip | |
podman kube play allow --network host
I see no reason to block --network host with kube play and force users
to have to set it in the yaml file.
This is just confusing when compared to the other podman create/run
--network options, see discussion in #15945.
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'pkg/domain/infra')
| -rw-r--r-- | pkg/domain/infra/abi/play.go | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/pkg/domain/infra/abi/play.go b/pkg/domain/infra/abi/play.go index 4a83cb464..8779acfda 100644 --- a/pkg/domain/infra/abi/play.go +++ b/pkg/domain/infra/abi/play.go @@ -344,10 +344,6 @@ func (ic *ContainerEngine) playKubePod(ctx context.Context, podName string, podY return nil, err } - if (ns.IsBridge() && len(networks) == 0) || ns.IsHost() { - return nil, fmt.Errorf("invalid value passed to --network: bridge or host networking must be configured in YAML") - } - podOpt.Net.Network = ns podOpt.Net.Networks = networks podOpt.Net.NetworkOptions = netOpts |