How to deploy specific calico version on openshift 4.x about operator HOT 4 CLOSED

@dbazhal the intended behavior is that each operator version corresponds to a particular Calico version. To update the Calico version, simply bump the version of the operator that you are running to one that installs the Calico version you want.

from operator.

This is intentional, since it guarantees that the config that is deployed matches and has been tested against the code it is deploying. If we allowed the operator to install arbitrary images, that would expose users to an opportunity to break their cluster by installing a version that isn't compatible with the way the operator config.

from operator.

@caseydavenport ill look through the code and releases but are those calico tags easily retrievable? I'm trying to do air gapped deploys of calico operator and it'd be great if I had a straightforward to deploy what they are during staging.

from operator.

The notes with each release are expected to have the Calico version the release includes. So looking through the releases should give you that information.

from operator.