From 6c10ad3db10faf7c74a0cbf81ec33bcdb3333b9e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Elisamara=20Aoki=20Gon=C3=A7alves?= Date: Mon, 15 Sep 2025 16:49:56 +0000 Subject: [PATCH] ptp-notification upversion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fix image in output. Story: 2011332 Task: 52123 Change-Id: Id74829752a1c4dceb9dcce40ef9e4ba5aea65dd9 Signed-off-by: Elisamara Aoki Gonçalves --- ...e-application-with-notification-client-sidecar.rst | 11 ++++++----- .../kubernetes/ptp-notifications-overview.rst | 6 +++--- 2 files changed, 9 insertions(+), 8 deletions(-) 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 f6420d50c..9a1d1640e 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 @@ -40,7 +40,7 @@ application and the Sidecar communicate via a REST API. See the figure below. To use the v1 API, deploy ``starlingx/notificationclient-base:stx.5.0-v1.0.4`` as the sidecar container. -To use the v2 API, deploy ``starlingx/notificationclient-base:stx.9.0-v2.1.1`` +To use the v2 API, deploy ``starlingx/notificationclient-base:stx.11.0-v2.3.3`` as the sidecar container. .. rubric:: |prereq| @@ -68,9 +68,10 @@ configured to make API calls to the notificationclient-base container. .. note:: - The following example is for ``ptp-notification`` v2 API. To integrate - with ``ptp-notification`` v1 API, change the image from ``starlingx/notificationclient-base:stx.9.0-v2.1.1`` - to ``starlingx/notificationclient-base:stx.5.0-v1.0.4``. + The following example is for ``ptp-notification`` v2 API. To integrate with + ``ptp-notification`` v1 API, change the image from + ``starlingx/notificationclient-base:stx.11.0-v2.3.3`` to + ``starlingx/notificationclient-base:stx.5.0-v1.0.4``. .. note:: @@ -109,7 +110,7 @@ configured to make API calls to the notificationclient-base container. - "true" containers: - name: ptp-notification-demo-sidecar - image: "starlingx/notificationclient-base:|v_starlingx-notificationclient-base|" + image: "starlingx/notificationclient-base:stx.11.0-v2.3.3" imagePullPolicy: IfNotPresent tty: true stdin: true diff --git a/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst b/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst index 62fb001a5..12c9c8273 100644 --- a/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst +++ b/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst @@ -161,15 +161,15 @@ deploys two ``notificationservice-base`` containers to support these APIs. Users must decide which API they will use by deploying the appropriate ``notificationclient-base`` image as a sidecar with their consumer application. -- The v1 API uses ``starlingx/notificationservice-base:stx.9.0-v2.1.1`` +- The v1 API uses ``starlingx/notificationservice-base:stx.11.0-v2.2.8`` - Compatible with the image: ``starlingx/notificationclient-base:stx.5.0-v1.0.4`` -- The v2 API uses ``starlingx/notificationservice-base-v2:stx.9.0-v2.1.1`` +- The v2 API uses ``starlingx/notificationservice-base-v2:stx.11.0-v2.4.5`` - Compatible with the image: - ``starlingx/notificationclient-base:stx.9.0-v2.1.1`` + ``starlingx/notificationclient-base:stx.11.0-v2.3.3`` Upgrades of |prod| |prod-ver| to the next patch will automatically upgrade the ``ptp-notification`` application and deploy both the v1 and v2 API containers.