podman generate kube - YAML when without shared network

[fdvhet]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

I am not sure if this is a bug, not added feature intentionally or feature not yet implemented.
podman generate kube for pod without shared network produces YAML file which doesn't reproduce pod state when "played".

Steps to reproduce the issue:

1. podman pod create --name nginxs-pod --replace=true --share pid,ipc,uts

2. podman run --detach -t --pod nginxs-pod --name nginx1 --replace=true -p 30080:80/TCP --rm=true docker.io/library/nginx:latest

3. podman run --detach -t --pod nginxs-pod --name nginx2 --replace=true -p 30081:80/TCP --rm=true docker.io/library/nginx:latest

4. podman generate kube nginxs-pod > nginxs-pod.yaml

5. podman pod rm -f nginxs-pod

6. podman play kube nginxs-pod.yaml

Describe the results you received:

IMAGE                           COMMAND               CREATED        STATUS            PORTS       NAMES
k8s.gcr.io/pause:3.5                                  6 seconds ago  Up 3 seconds ago              6582b85b15e6-infra
docker.io/library/nginx:latest  nginx -g daemon o...  4 seconds ago  Up 3 seconds ago              nginxs-pod-nginx2

nginx1 is not available (because of Address already in use).

Describe the results you expected:

IMAGE                           COMMAND               CREATED         STATUS             PORTS                  NAMES
k8s.gcr.io/pause:3.5                                  37 seconds ago  Up 15 seconds ago                         ada9c5c3d567-infra
docker.io/library/nginx:latest  nginx -g daemon o...  15 seconds ago  Up 15 seconds ago  0.0.0.0:30080->80/tcp  nginx1
docker.io/library/nginx:latest  nginx -g daemon o...  3 seconds ago   Up 2 seconds ago   0.0.0.0:30081->80/tcp  nginx2

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

Output of podman version:

$ podman version
Version:      3.3.0-rc1
API Version:  3.3.0-rc1
Go Version:   go1.16.6
Built:        Thu Jan  1 00:00:00 1970
OS/Arch:      linux/amd64

Output of podman info --debug:

$ podman info --debug`
host:
  arch: amd64
  buildahVersion: 1.22.0-dev
  cgroupControllers: []
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.27, commit: '
  cpus: 2
  distribution:
    distribution: ubuntu
    version: "21.04"
  eventLogger: journald
  hostname: localhost
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.11.0-31-generic
  linkmode: dynamic
  memFree: 2922130944
  memTotal: 4338903040
  ociRuntime:
    name: crun
    package: 'crun: /usr/bin/crun'
    path: /usr/bin/crun
    version: |-
      crun version 0.20.1.5-925d-dirty
      commit: 0d42f1109fd73548f44b01b3e84d04a279e99d2e
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    path: /tmp/podman-run-1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: 'slirp4netns: /usr/bin/slirp4netns'
    version: |-
      slirp4netns version 1.1.8
      commit: unknown
      libslirp: 4.3.1-git
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.1
  swapFree: 9832887
  swapTotal: 9832887
  uptime: 1h 0m 18.27s (Approximately 0.04 days)
registries:
  search:
  - docker.io
  - quay.io
store:
  configFile: /home/pod/.config/containers/storage.conf
  containerStore:
    number: 4
    paused: 0
    running: 2
    stopped: 2
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/pod/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 2
  runRoot: /tmp/podman-run-1000/containers
  volumePath: /home/pod/.local/share/containers/storage/volumes
version:
  APIVersion: 3.3.0-rc1
  Built: 0
  BuiltTime: Thu Jan  1 00:00:00 1970
  GitCommit: ""
  GoVersion: go1.16.6
  OsArch: linux/amd64
  Version: 3.3.0-rc1

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

$ apt list podman
Listing... Done
podman/unknown,now 100:3.2.3-3 amd64 [installed]
podman/unknown 100:3.2.3-3 arm64
podman/unknown 100:3.2.3-3 armhf
podman/unknown 100:3.2.3-3 s390x

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

[Luap99]

Does the k8s yaml has support for specifying which namespaces should be shared? I only found this https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#hosts-namespaces

[mheon]

This one may be outside what Kube YAML can do. I expect we're going to run into this more and more as we start to push the boundaries with play kube - probably worth a discussion with the team about approach on issues like this. @baude @rhatdan WDYT?

[rhatdan]

Yes I think we need to say that certain features that are not implemented in kubernetes, will not translate back into generate kube, because they can not.
podman pod create pods are not completely identical to Kubernetes Pods. Similarly containers can not be created identically.

[fdvhet]

Thanks for the answers!

This is what I expected. Maybe kind of warning for not translatable features during podman generate kube might be added to inform about this?

What command should be used instead to dump set of settings for further usage? podman-compose?

[github-actions[bot]]

A friendly reminder that this issue had no activity for 30 days.

[github-actions[bot]]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

This is not really an issue, and I hesitate to have warning about missing features, because we will miss many. Lets continue the conversation as a discussion.