You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My concern here is for the new installations, should we choose 3.28.0 or the current release marked as latest.
Just getting condused on the major release number 3.28.
For example, if we go with 3.27.4 for new installations as its marked latest, does it have bug fixes for 3.28.0?
Currently test clusters are running with 3.28.0.
Further testing for new installations should we go with 3.27.4?
Automation uses the manifest file from the calico project where we update the latest version. https://github.com/projectcalico/calico/v3.28.0/manifests/tigera-operator.yaml
For newer installation for testing should we go with 3.27.4?
Thank you for your clear information on this.
Hope they could adapt this as a feature in GitHub itself.
Something like latest release marking, for each bug fix patch versions of manjor.minor releases for Semantic Versioning.
My concern here is for the new installations, should we choose 3.28.0 or the current release marked as latest.
Just getting condused on the major release number 3.28.
For example, if we go with 3.27.4 for new installations as its marked latest, does it have bug fixes for 3.28.0?
Currently test clusters are running with 3.28.0.
Further testing for new installations should we go with 3.27.4?
Automation uses the manifest file from the calico project where we update the latest version.
https://github.com/projectcalico/calico/v3.28.0/manifests/tigera-operator.yaml
For newer installation for testing should we go with 3.27.4?
This issue is continuation of #8999
I was unable to reopen the above issue, hence opened this new issue to get a clear picture on this.
Please assist us on this query.
The text was updated successfully, but these errors were encountered: