commit 4a9710600d7dfd1c12d92695dbfedff619ce482a
Author: Dan Voiculeasa <email address hidden>
Date: Fri May 21 14:03:30 2021 +0300
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.
Reviewed: https:/ /review. opendev. org/c/starlingx /stx-puppet/ +/792582 /opendev. org/starlingx/ stx-puppet/ commit/ 4a9710600d7dfd1 c12d92695dbfedf f619ce482a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 4a9710600d7dfd1 c12d92695dbfedf f619ce482a
Author: Dan Voiculeasa <email address hidden>
Date: Fri May 21 14:03:30 2021 +0300
Change pod pid limit default value
Change the behavior of kubernetes pod pid limit in case the service
parameter is missing.
The initial change( I10c1684fe3145e 0a46b011f8e87f7 a23557ddd4a) 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 63475b926242a6f a7192addd56
Related-Bug: 1928353
Signed-off-by: Dan Voiculeasa <email address hidden>
Change-Id: I0f776d9a8be573