diff --git a/doc/source/guest_integration/kubernetes/integrate-application-with-notification-client-sidecar.rst b/doc/source/guest_integration/kubernetes/integrate-application-with-notification-client-sidecar.rst index c905b3041..be651b2e5 100644 --- a/doc/source/guest_integration/kubernetes/integrate-application-with-notification-client-sidecar.rst +++ b/doc/source/guest_integration/kubernetes/integrate-application-with-notification-client-sidecar.rst @@ -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: diff --git a/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst b/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst index 897982433..5fcdff268 100644 --- a/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst +++ b/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst @@ -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