Fix pod max pids service parameter default value

Openstack installation fails for rabbit-mq pods.

Change the approach of how the default value is selected.
Document recommended minimum values for apps instead of using them.
Select the default value as high as possible, protecting against a
rogue pod, protecting against platform slowdowns created by high number
of processes in the system, but low enough such that platform is still
responsive even on older hardware.
User is free to decrease the limit to increase the degree of protection
against slowdowns.

Initially it was observed that openstack pods reach ~450 processes
in steady state.
New tests show even with the 2/3 extra room, 750 pid limit is not
sufficient when deploying rabbit-mq pods. But 2000 is.
Recommended minimum value for openstack pods pid limit becomes 2000.

Partial-Bug: 1928949
Related-Bug: 1928353
Signed-off-by: Dan Voiculeasa <dan.voiculeasa@windriver.com>
Change-Id: I0d66173e2247fae15eda1ad0e83c7bcf858f0369
This commit is contained in:
Dan Voiculeasa 2021-05-21 12:56:47 +03:00
parent fcb6d5f35f
commit 8423e70fd0
1 changed files with 4 additions and 2 deletions

View File

@ -1126,8 +1126,10 @@ SERVICE_PARAM_SECTION_KUBERNETES_CONFIG = 'config'
SERVICE_PARAM_NAME_KUBERNETES_POD_MAX_PIDS = 'pod_max_pids'
# Platform pods use under 20 in steady state, but allow extra room.
SERVICE_PARAM_KUBERNETES_POD_MAX_PIDS_MIN = 100
# Some openstack pods reach ~450 in steady state, allow 2/3 extra to be safe.
SERVICE_PARAM_KUBERNETES_POD_MAX_PIDS_DEFAULT = 750
# Account for uncontrolled changes in applications (e.g. stx-openstack) by
# setting a very large number. Will document the recommended minimum value
# for supported applications.
SERVICE_PARAM_KUBERNETES_POD_MAX_PIDS_DEFAULT = 10000
SERVICE_PARAM_KUBERNETES_POD_MAX_PIDS_MAX = 65535
SERVICE_PARAM_SECTION_KUBERNETES_CERTIFICATES = 'certificates'