bb5cf99f7b
Included information from msg attached to Jira in Edited content in Admin tasks and User tasks Patch 1: worked on comments by Greg. Patch 4: added User task to the correct branch Patch 5: worked on feedback from Greg also in other topics Edited content in: -helm client for non-admin users -container backed remote clis and clients -install kebectl and helm clients on a host Patch 6: edited and added content in -helm client for non-admin users Patch 7: Added content in: Configure remote CLI Configure container-backed... Use container-backed... Patch 10: acted on Jim's comment and removed topic 'create, test, and terminate a ptp notification demo' removed links to this topic Patch 11: acted on Greg's comments Patch 12: acted on Greg's comments Story: 2007000 Task: 42241 https://review.opendev.org/c/starlingx/docs/+/783891 Signed-off-by: Adil <mohamed.adilassakkali@windriver.com> Change-Id: I9a5faf5549775593ddfd517d43412725d257b24f
1.3 KiB
1.3 KiB
Integrate the Application with Notification Client Sidecar
This section describes the ptp-notification-demo, and provides instructions for enabling communication between the Sidecar and the application via a REST API.
The integration between the application is done with the use of a Sidecar. The Sidecar runs as a container along with the application in the same pod. The application and the Sidecar communicate via a REST API. See the figure below.
Note
In this demo, we provide a referenced API application.
The following prerequisites are required before the integration:
- The cloud is configured with a node that supports the Subordinate mode (Slave mode).
- The cloud is labeled with ptp-registration=true, and ptp-notification=true.
- The ptp-notification-armada-app application is installed successfully.
- The application supports the Notifications API.
