Hi Scott,
Thanks for the clarification!
If I remember correctly the message appeared after editing files in the WRP Management root and deploying the changes.
The message we see for other changes in the wrp are much more "explicit" -- they tell the names of the wrp containers that need to be restarted.
In a Kubernetes environment a 'clash' in nomenclature opens the playing field for some confusion.
"any runtime containers" when bound to the ISVA namespace (as you pointed out) refers to the runtime and AAC containers, but from a Kubernetes point of view also includes the wrp, config and dsc containers as they all are "Kubernetes runtime" containers.
Hence the question :-)
Rgds
------------------------------
Anders Domeij
CGI Sweden AB
------------------------------
Original Message:
Sent: Fri November 19, 2021 04:04 PM
From: Scott Exton
Subject: Wording in Warning message
Anders,
That message indicates that you need to start any federation/AAC runtime containers. A different message is displayed when you need to restart a WRP container.
What changes to the system were made to produce this message? WebSEAL changes should cause a different message to be displayed, asking you to restart the containers for the WRP instance which has been modified.
Scott A. Exton
Senior Software Engineer
Chief Programmer - IBM Security Verify Access
IBM Master Inventor
Original Message:
Sent: 11/19/2021 8:24:00 AM
From: Anders Domeij
Subject: Wording in Warning message
Hi,
ISVA 10.0.2.0 in a Kubernetes environment.
maybe a silly question, but after deploying changes made to the Reverse proxy configuration the following msg box is displayed.
Should we read this as restarting all isva-runtime(s), all deployed webseal reverse proxies containers or all (config,runtime wrp and dsc) ISVA containers?
Thanks in advance
------------------------------
Anders Domeij
CGI Sweden AB
------------------------------