Staying on Ignite 2 deliberately
Apache Ignite 3 is a substantially different system from Ignite 2, not an in-place upgrade. For most Ignite 2 estates, the pragmatic path is a supported 2.x, not a rewrite on a security deadline.
Challenge
Ignite 3 changed the architecture rather than iterating on it, and there is no straightforward in-place upgrade for an Ignite 2 deployment. That makes "move to 3" a rewrite project, which is not an answer to an open CVE.
Environment
Apache Ignite 2.x running production caching, compute or data-grid workloads.
Approach
OSSeva supports the Ignite 2.x line directly -- CVE patches on the version running -- so the decision about Ignite 3 gets made on architectural merit rather than under security pressure.
What this delivers
A supported Ignite 2 estate, with the Ignite 3 question separated from the patching question.