Using hostNetwork with play kube results in error

[bziemons]

/kind bug

Description

Using hostNetwork in pod yaml with play kube results in Error: namespace value host cannot be provided with namespace mode .

Steps to reproduce the issue:

1. Having the following simple pod.yaml:

apiVersion: v1
kind: Pod
metadata:
  labels:
    app: test
  name: test_pod
spec:
  hostNetwork: true
  containers:
    - name: test
      image: docker.io/alpine
      command: ["/bin/sh", "-c"]
      args: ["while true; do date; sleep 2; done"]

2. Using podman play kube pod.yaml

Describe the results you received:

The error: Error: namespace value host cannot be provided with namespace mode

Describe the results you expected:

I expected the pod to start in host network mode as happened with podman 2.1

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

podman version 3.0.0-dev

(same happens on the 2.2.1 release)

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.19.0-dev
  cgroupManager: systemd
  cgroupVersion: v1
  conmon:
    package: /usr/bin/conmon is owned by conmon 1:2.0.22-1
    path: /usr/bin/conmon
    version: 'conmon version 2.0.22, commit: 9c34a8663b85e479e0c083801e89a2b2835228ed'
  cpus: 8
  distribution:
    distribution: arch
    version: unknown
  eventLogger: journald
  hostname: lunar
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.9.14-zen1-1-zen
  linkmode: dynamic
  memFree: 1011572736
  memTotal: 33614442496
  ociRuntime:
    name: runc
    package: /usr/bin/runc is owned by runc 1.0.0rc92-1
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc92
      commit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
      spec: 1.0.2-dev
  os: linux
  remoteSocket:
    exists: true
    path: /run/podman/podman.sock
  rootless: false
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 0
  swapTotal: 0
  uptime: 4h 4m 47.03s (Approximately 0.17 days)
registries: {}
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageStore:
    number: 10
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 3.0.0
  Built: 1608469638
  BuiltTime: Sun Dec 20 14:07:18 2020
  GitCommit: 5c6b5ef34905f40562b518799c35be8d06694e65-dirty
  GoVersion: go1.15.6
  OsArch: linux/amd64
  Version: 3.0.0-dev

(again: same happens on 2.2.1 release)

Package info (e.g. output of rpm -q podman or apt list podman):

$ pacman -Si podman
Repository      : community
Name            : podman
Version         : 2.2.1-1
Description     : Tool and library for running OCI-based containers in pods
Architecture    : x86_64
URL             : https://github.com/containers/libpod
Licenses        : Apache
Groups          : None
Provides        : None
Depends On      : cni-plugins  conmon  containers-common  device-mapper  iptables  libseccomp  runc  slirp4netns  libsystemd  fuse-overlayfs  libgpgme.so=11-64
Optional Deps   : podman-docker: for Docker-compatible CLI
                  btrfs-progs: support btrfs backend devices
                  catatonit: --init flag support
                  crun: support for unified cgroupsv2
Conflicts With  : None
Replaces        : None
Download Size   : 19,57 MiB
Installed Size  : 79,09 MiB
Packager        : Morten Linderud <[email protected]>
Build Date      : Di 08 Dez 2020 22:48:23 CET
Validated By    : MD5 Sum  SHA-256 Sum  Signature

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.):

happens on two physical machines.