This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
In the current design, once the status in gwv6 Pod is transitioned into Terminating, SIGTERM signal is sent to gwv6 Pod. And if this process is not completed within 30s (=terminationGracePeriodSeconds), SIGKILL signal is sent to gwv6 Pod by compulsion. Based on my previous customer's verification on IBM Cloud Private or my internal verification on EKS, when gwv6 Pod is restarted, very few APIs (0.052% - 0.094%) are returned as errors.
To seek for any work-arounds, firstly, I tried to inject following snippets into gatewaycluster.gateway.apiconnect.ibm.com/gwv6, but it was not permitted. So, I tried to do that for StatefulSet (gwv6) and it was successful.
With the above lifecycle, when gwv6 Pod is restarted, all APIs are returned as 200. Unfortunately, however, when we apply FixPack, StatefulSet is overwritten, which means StatefulSet is backed to the default. Eventually, preStop setting is discarded and I see the same error situation.
Do not place IBM confidential, company confidential, or personal information into any field.