IKO (Iris Kubernetes Operator) Service not redirecting dynamically to the correct Pod
In the context of IKO (Iris Kubernetes Operator) the question of Service not redirecting dynamically to the correct Pod is still pending.
In production this can be dangerous since an overload (or any other simpler problem) can cause you to change the main Pod and leave the application inoperable until we intervene.
Intersystems support warned that this is still an issue of IKO, but there are some possibilities that I am studying.
To explore an idea I had, I would like the help of this Forum to answer the following question:
Is there a way, via the non-iterative command line, to detect whether the current Iris instance is a primary member of Mirror or a backup?
I imagine it would be enough if I could detect whether a particular database is write-protected or not ...
I have access to the Linux terminal of the host machine with the "iris", "irissession" and other applications present or that can be installed.