-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[WIP] 🌱 Stop setting and relying on TypeMeta in typed objects #12533
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
base: main
Are you sure you want to change the base?
[WIP] 🌱 Stop setting and relying on TypeMeta in typed objects #12533
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Pausing the work on this for now, will get back to it in a bit |
Signed-off-by: Stefan Büringer [email protected]
Signed-off-by: Stefan Büringer [email protected]
9501b0a to
4c6c105
Compare
|
/test pull-cluster-api-e2e-main |
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
controller-runtime and k8s.io/* generally don't set TypeMeta on typed objects. So we should stop relying on it being set. Accordingly we should also not set it on typed objects in tests.
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 #