Hi Team,

IHAC, They would like upgrade the OSSM to 2.3.9 [ latest 2.3.z version ] from OSSM 2.3.3 [ Current version ] 

But upgrading to 2.3.9 is not possible since image is not available :
Channel: stable (default)

Current Version:
2.4.5

Other Available Versions

2.4.4

2.4.3

2.4.2

2.4.1

2.4.0

2.3.3

2.3.2

2.3.1

2.3.0

2.2.3

2.2.2

2.2.1

2.2.0

2.1.3

2.1.2

2.1.1

2.1.0

2.0.8
 
I also tested the installation and upgrade process for 2.3.9 from 2.3.3 and got the error not found operator image if I try to upgrade to OSSM 2.3.9 and also if I were to install OSSM 2.3.9 due to which team can only upgrade to above versions.

[ Customer Impact: ]
Still few of application are running on service mesh control plane versions v2.0 ,v2.1,v.2.2.
if we upgrade to ossm v2.4, applications running in production will have outage. impact the business if all the pods stop running.
[ Customer Challenges ] 

• 4.12's release notes points to multiple maintenance release available greater than 2.3.3  and currently team can't upgrade to 2.3.9 due to no availability to upgrade to 2.3.9 from 2.3.3 .
• In order for customer to do maintenance level upgrade of their 4.12 version to close open vulnerabilities with the current 4.12 version installed, They may need to again skip updating OSSM as this is taking longer than they expected and their window to do their upgrade is quickly closing.

[ Customer require help at ] 

• Customer can upgrade to latest 2.3.9 version from 2.3.3 from channel path
• This would be so much easier to manage if there was a channel-2.3 and channel-2.4 so that customer can pick the time to update and still get maintenance releases for the channel they are on  Because there is only a "stable" you are forced to update to the latest OSSM version without truly knowing the impact of the new version might have on the current meshes, specifically the SMCP in use.

Team please let me if this is possible to implement for the channel part and also the upgrade to 2.3.9