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

🌱 Apply embedded capi feature flag after rancher install #190

Merged

Conversation

Danil-Grigorev
Copy link
Contributor

@Danil-Grigorev Danil-Grigorev commented Oct 4, 2023

kind/chore

What this PR does / why we need it:
This PR converts all existing gitops scenarios to a rancher installation with post-install step applying required feature gates as per documented installation process.

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 #188

Special notes for your reviewer:

Checklist:

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

@Danil-Grigorev Danil-Grigorev requested a review from a team as a code owner October 4, 2023 11:26
@Danil-Grigorev Danil-Grigorev force-pushed the apply-fg-after-rancher-setup branch 2 times, most recently from 64d7c87 to dd50762 Compare October 4, 2023 11:52
@alexander-demicev
Copy link
Member

will this fail e2e until webhooks are fixed in rancher?

@Danil-Grigorev
Copy link
Contributor Author

will this fail e2e until webhooks are fixed in rancher?

Yes, until the implementation part is done the e2e tests would fail to apply CAPI cluster with this coming from fleet logs:

2023-10-04T12:02:42.442248697Z stderr F time="2023-10-04T12:02:42Z" level=error msg="error syncing 'cluster-fleet-local-local-1a3d67d0a899/repo-creategitops-eclnmh-clusters': handler bundle-deploy: failed to create resource: Internal error occurred: failed calling webhook \"default.cluster.cluster.x-k8s.io\": failed to call webhook: Post \"https://webhook-service.cattle-system.svc:443/mutate-cluster-x-k8s-io-v1beta1-cluster?timeout=10s\": service \"webhook-service\" not found, requeuing"

@richardcase
Copy link
Contributor

Until we have that feature in Rancher turtles we can always use RunCommand to run the following after disabling the feature and waiting for the Rancher CAPI deployment to be removed:

kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io mutating-webhook-configuration
kubectl delete validatingwebhookconfigurations.admissionregistration.k8s.io validating-webhook-configuration

@richardcase
Copy link
Contributor

Or we just wait for the feature to be added 😉

@alexander-demicev
Copy link
Member

@richardcase should we have a controller temporarily like this one #178 to require less setup from users?

salasberryfin
salasberryfin previously approved these changes Oct 5, 2023
salasberryfin
salasberryfin previously approved these changes Oct 6, 2023
salasberryfin
salasberryfin previously approved these changes Oct 9, 2023
@Danil-Grigorev Danil-Grigorev merged commit 8b8ecf3 into rancher:main Oct 9, 2023
8 checks passed
Danil-Grigorev added a commit to Danil-Grigorev/rancher-turtles that referenced this pull request Oct 9, 2023
Danil-Grigorev added a commit to Danil-Grigorev/rancher-turtles that referenced this pull request Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[E2E] Add a test that covers already existing Rancher Manager cluster
4 participants