What happened?

With the new feature to disable hostport mapping on CRI-O to delegate the functionality to CNI, the expectation is to send the portmappings into the CNIPlugin.SetUpPodWithContext. CNI does not receive the host portmappings configuration.

What did you expect to happen?

Set portmappings in run time config field before delegating the functionality to CNI

How can we reproduce it (as minimally and precisely as possible)?

set disable_hostport_mapping = true in crio.conf, Use portmap CNI plugin from https://github.com/containernetworking/plugins, Set pod spec to use a hostportmap. Expectation is that CRI-O delegates the task to CNI plugin with right runtime config. IPtable rules from portmap plugin is added to NAT table

Anything else we need to know?

No response

CRI-O and Kubernetes version

$ crio --version
RuntimeName:  cri-o
RuntimeVersion:  1.27.0
RuntimeApiVersion:  v1

OS version

# On Linux:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Additional environment details (AWS, VirtualBox, physical, etc.)