11.1.1 Container Gateway images tags
Article ID: 379842
Updated On:
Products
Issue/Introduction
On product doc page:
We have the following for "Gateway Docker Tag Summar":
MPP for Gateway 11.1.1 (September 2024) latest, 11.1.1, 11.1.00_20240930
MPP for Gateway 11.1.1 (August 2024) 11.1.00_20240830
Gateway 11.1.1 (includes applicable platform patches) 11.1.1_20240806
Here we can see that the initial 11.1.1 has the docker tag as 11.1.1_20240806. However, both August and September MPPs are now using 11.1.00_yyyymmdd for their tags.
This creates confusion for some customers and causes patching failure for others.
Environment
CA APIM Gateway Container Form Factor
Cause
11.1.1_20240806 is creating a confusion but that was a glitch from our engineering side on that tag. We understood that but did not rectify because already customers started using it.
Resolution
The rationale behind this is the following:
Tags generally named on top of the major release. If you see 11.0 tags, they are like 11.0.00_CR3, 11.0.00_20240930. But for 11.1, we moved out of the CR naming convention. So 11.1.1 is ideally 11.1 CR01. If we put a tag like 11.1.1_20240930, then it ideally comes like 11.1CR1_20240930 which we never followed earlier (for example 11.0 or 10.1 releases).
Essentially, the 11.1.1_0240806 is a glitch(bug), the 11.1.00_yyyymmdd tagging pattern is what will be followed from now for the upcoming MPPs. Customers are advised to use this new pattern.
Feedback
