Updated PTP sidecar container liveness probe timeouts (r6, r7, r8, dsr6, dsr7, dsr8)

Updated patchset 2 comments
Updated Patchset 1 comments

Change-Id: I8aa338d89137b7d53ff7e8a37f1fb964f74684c7
Signed-off-by: Juanita Balaraj <juanita.balaraj@windriver.com>
This commit is contained in:
Juanita Balaraj 2023-11-21 21:36:07 +00:00
parent 85b72a3531
commit a089f6bbfe
2 changed files with 10 additions and 9 deletions

View File

@ -109,14 +109,13 @@ configured to make API calls to the notificationclient-base container.
livenessProbe:
exec:
command:
- timeout
- "2"
- curl
- http://127.0.0.1:8080/health
failureThreshold: 3
periodSeconds: 3
initialDelaySeconds: 30
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 3
timeoutSeconds: 5
env:
- name: THIS_NODE_NAME
valueFrom:

View File

@ -103,7 +103,11 @@ probe, if required. You can edit the Sidecar values in the deployment
manifest to include these parameters.
.. note::
Port and timeout values can be configured to meet user preferences.
The ``periodSeconds`` and ``timeoutSeconds`` values can be adjusted based
on system performance. A shorter value places more resource demand on the
Sidecar pod, so longer values can improve pod stability.
.. code-block:: none
@ -116,17 +120,15 @@ manifest to include these parameters.
livenessProbe:
exec:
command:
- timeout
- "2"
- curl
- http://127.0.0.1:8080/health
failureThreshold: 3
periodSeconds: 3
initialDelaySeconds: 30
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 3
timeoutSeconds: 5
EOF
**Container images and API compatibility**
The ``ptp-notification`` provides a v1 API for backwards compatibility with