1. Proposed title of this feature request
   RLIMIT support for containers (cri-o/containerd) in Openshift

1.  What is the nature and description of the request?
   At the system level, the number of connections or sockets are constrained by the number of file descriptors a process is allowed to open: RLIMIT_NOFILE

1.  Why does the customer need this? (List the business requirements here)
   Scenario: a developer created an app connecting to a DB, which was not implemented properly and instead of opening just 1 connection, it was a loop of connections. So this pod caused nf_conntrack_use to reach nf_conntrack_max in the node, and therefore, no more connections could be opened. So the node got frozen, and it was needed to have the node rebooted.

1.  List any affected packages or components.
   cri-o/containerd
   Runtimes

----The customer's main concern is:
There are a lot of upstream on-going work, so we´d like you to open an RFE about this. This way Engineering could track or even could contribute to all the upstream work (cri-o, kuberntes), and integrate/support in Openshift.
Findings:

This is not supported in Kubernetes (per container) yet: https://github.com/kubernetes/kubernetes/issues/3595

Its configuration is not supported by cri-o: https://github.com/cri-o/cri-o/blob/main/docs/crio.conf.5.md#crioruntime-table

Not by containerd yet: https://github.com/containerd/containerd/pull/6064

It is not configurable in OpenShift (global container engine): https://docs.openshift.com/container-platform/4.8/post_installation_configuration/machine-configuration-tasks.html#create-a-containerruntimeconfig_post-install-machine-configuration-tasks