Change pod pid limit default value
Change the behavior of kubernetes pod pid limit in case the service parameter is missing. The initial change(I10c1684fe3145e0a46b011f8e87f7a23557ddd4a) proposed a value to protect the system by default in case the service parameter was missing. The value was aligned with what was believed to work for StarlingX apps. Some apps, openstack for example, are upstream and StarlingX doesn't control changes inside them. Instead of maintaining the value initially proposed here, change the approach. Change the behaviour to use the maximum value for the service parameter by default. Partial-Bug: 1928949 Related-Bug: 1928353 Signed-off-by: Dan Voiculeasa <dan.voiculeasa@windriver.com> Change-Id: I0f776d9a8be57363475b926242a6fa7192addd56
This commit is contained in:
parent
3d9fc64991
commit
4a9710600d
@ -17,7 +17,7 @@ class platform::kubernetes::params (
|
||||
$k8s_topology_mgr_policy = 'best-effort',
|
||||
$k8s_cni_bin_dir = '/usr/libexec/cni',
|
||||
$k8s_vol_plugin_dir = '/usr/libexec/kubernetes/kubelet-plugins/volume/exec/',
|
||||
$k8s_pod_max_pids = '750',
|
||||
$k8s_pod_max_pids = '65535',
|
||||
$join_cmd = undef,
|
||||
$oidc_issuer_url = undef,
|
||||
$oidc_client_id = undef,
|
||||
|
Loading…
x
Reference in New Issue
Block a user