AES issue in OpenShift cloud
Hello,
I am informed that AES has a problem running on open-shift (cloud), since the virtual nature changes the pod ID on server bounces. Has anyone encountered this? Is there a resolution?
I would like to promote wider AES usage at my company, but we are moving to Open Shift, and this becomes a challenge.
Pegasystems Inc.
IN
Hello
I am not sure about the challenges involved, but i think you can think of using : Pega predictive diagnostic cloud as well.
Refer the below links for details :
https://community.pega.com/video-library/pega-predictive-diagnostic-cloud-product-overview
https://collaborate.pega.com/discussion/pega-predictive-diagnostic-cloud-configuration-application
https://community.pega.com/marketplace/components/predictive-diagnostic-cloud
Pegasystems Inc.
US
Ivan,
Can you elaborate on who informed the AES problem on open-shift? Is this from pega resources or open-shift (redhat)?
UHG
US
Our team that installs, and sets up pega and pega frameworks. They have been involved in getting Pega to work on Open-Shift. This is one of the problems they identified.
Pegasystems Inc.
US
Thanks, Ivan. I think it would be more helpful if your team can articulate the details. I do not believe we (pega) have deployed AES on open-shift. Karen Davie, any insights on this? We would definitely want to know if this issue can be avoided through some environment specific configuration (likely on the networking side) so that there would be no need for any product changes. What version of AES are you installing?
UHG
US
At this point in time, this was an attempt to find if someone had encountered this, and had a solution (fishing). The detailed definition I have is incomplete, though I would assume of someone had encountered and solved this, I could leverage that. For us, this is not yet a priority to solve, it only helps spread AES usage, a goal of our COE. One can work around not using AES on open shift. If someone encounters this problem before it becomes a priority for us, that would be helpful. Otherwise, we might be early on being main stream on this issue.
In your tracking of MESH usage, I'm not sure if leaving this out for future encounters is helpful, or we remove this.