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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
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.
If we modify and persist preStop option, in-flight transactions might be completed before before the DataPower goes down. It means that we won't see several errors during applying FixPack.
Do not place IBM confidential, company confidential, or personal information into any field.