-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
✨ Integrate CRS code into regular code structure #11943
Conversation
I'm getting many lint issues with:
can i disable this? |
@mcbenjemaa In general yes by changing excludes. But I should have them fixed until tomorrow on main. So I would just ignore them for now and then rebase |
#11909 is merged Afterwards there should be no other PRs conflicting with this PR. But I think if you have time already we can already try to get this PR into a state where tests and e2e tests are green (as I mentioned linter can be ignored for now, I would take another look after both other PRs are merged) |
How, we can fix |
Doesn't have to be fixed. apidiff just shows the API differences. It's then up to maintainers to determine if the changes are intended / acceptable. At a first glance it looks like they are, but I'll double check when I review the PR itself These two are much more important: |
I will ignore all |
@mcbenjemaa Started the CAPI controller locally with tilt. It doesn't come up because of this error
Basically the SetupWebhookWithManager funcs in alias.go are calling themselves. They should call the corresonding SetupWebhookWithManager func's in the internal/webhooks package instead |
Regarding pull-cluster-api-e2e-blocking-main I tested in my local machine, but I'm getting another error. |
You are right 😄 |
what's wrong with netlify |
Not sure. But I would just ignore Netlify. Usually it always works but once in a month it fails with something. In this case
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a quick review. I think these findings should fix the test failures as well
@mcbenjemaa #11949 merged. Let's rebase on top of main. I think that was the last PR that had conflict potential |
@sbueringer thanks for your notes. |
@mcbenjemaa Btw feel free to squash |
Regarding the findings here: https://github.com/kubernetes-sigs/cluster-api/actions/runs/13833818179/job/38704018628?pr=11943 You can simply add the Line 89 in afd68cd
|
/test pull-cluster-api-test-main I think this one is an unrelated flake So unit tests seems to be fine, but I think we'll need the linter fixes to get everything green (especially e2e tests) (expectation is that we should be able to get the linter green now with some fixes + #11943 (comment)) |
Refactor: MOVE CRS to his own addons group Fix go licenses Fix webhook alias SetupWebhookWithManager call Fix envtest, add addonsv1 scheme Fix Test_* with no addonsv1 scheme Fix APIGroup for addonsv1 Address reviews and fix missing imports Generate API Fix CRS controllers call
@mcbenjemaa: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Should be ready. |
/test pull-cluster-api-e2e-main |
Thank you very much! /lgtm /hold cancel |
LGTM label has been added. Git tree hash: f1dc68474ccd10e890bb013c755503a7679a2ab0
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@mcbenjemaa Thank you very much! |
What this PR does / why we need it:
This PR moves the CRS code from addons to regular CAPI including api and controllers.
Ref: #11114 (comment)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Closes #11114
/area clusterresourceset
/cc @fabriziopandini sbueringer