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

🌱 Install capi-operator as a turtles dependency in a dev-env #869

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

Danil-Grigorev
Copy link
Contributor

What this PR does / why we need it:

Improves dev environment setup for turtles, making it use actual turtles chart capi-operator as a dependency, as opposed to installing upstream one separately.

This allows to rely on CAPIProvider versions when deploying providers, so incompatibility in providers matrix is eliminated based on centralization of the providers version management.

Additionally this makes dev-env adhere to supported configuration described in turtles docs (more closely), and improves development process for etcd snapshot restore and other features.

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 #

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>
@Danil-Grigorev Danil-Grigorev requested a review from a team as a code owner November 25, 2024 12:50
@Danil-Grigorev Danil-Grigorev changed the title 🌱 Install turtles in a dev-env as opposed to upstream operator 🌱 Install turtles capi-operator in a dev-env as opposed to upstream operator Nov 25, 2024
@Danil-Grigorev Danil-Grigorev changed the title 🌱 Install turtles capi-operator in a dev-env as opposed to upstream operator 🌱 Install capi-operator as a turtles dependency in a dev-env Nov 25, 2024
@Danil-Grigorev Danil-Grigorev merged commit f91f27e into rancher:main Nov 27, 2024
9 checks passed
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.

3 participants