🌱 Make latest check optional behind followLatest field #688
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Follow up on #673. This change allows to selectively enable
followLatest
version behavior by setting the field in the spec. The behavior will be enabled by default forrancher/turtles
CAPIProviders
shipped with the helm chart installation, but will need a UI support, in order to set this field.Latest version is determined and limited by the state of the
clusterctl.yaml
file, preventing occasions of unbounded latest version installation, and so always follows the max version from theclusterctl-config
ConfigMap
.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #691
Special notes for your reviewer:
Checklist: