starlingx/docs
Code Issues Proposed changes

Merge "ptp-notification upversion"

Browse Source
This commit is contained in:
Zuul
2025-09-18 20:22:31 +00:00
committed by Gerrit Code Review
parent deff43bf9d 6c10ad3db1
commit ba1cab6e75
2 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/guest_integration/kubernetes/integrate-application-with-notification-client-sidecar.rst
View File

@@ -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

6
doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst
View File

@@ -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.