Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🌱 Make latest check optional behind followLatest field #688

Closed

Conversation

Danil-Grigorev
Copy link
Contributor

@Danil-Grigorev Danil-Grigorev commented Aug 26, 2024

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 for rancher/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 the clusterctl-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:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
@alexander-demicev
Copy link
Member

@Danil-Grigorev there is conflict now in Makefile

Copy link
Contributor

@furkatgofurov7 furkatgofurov7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, however, needs a rebase

@salasberryfin
Copy link
Contributor

@Danil-Grigorev can you take a look at the conflicts on this pr?

@Danil-Grigorev
Copy link
Contributor Author

Alternative overrides based implementation is merged #751, this can be closed, and followed-up with upstream implementation for determining non-overriden images version - kubernetes-sigs/cluster-api-operator#605

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Providers version not being updated with turtles upgrade
4 participants