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

clustermesh-apiserver: don't wait for the presence of unused CRDs #26220

Merged
merged 1 commit into from Jun 16, 2023

Conversation

giorio94
Copy link
Member

Currently, the clustermesh-apiserver waits for the presence of all the CRDs before starting the main logic, way more than the resource types actually used afterwards. This ends up preventing the possibility of running a newer version of the clustermesh-apiserver alongside older versions of cilium/cilium-operator due to newly introduced CRDs.

This PR modifies the logic to only wait for the CRDs which are actually used (the new list matches the entries listed in the clustermesh-apiserver cluster role).

clustermesh-apiserver: don't wait for the presence of unused CRDs

@giorio94 giorio94 added kind/cleanup This includes no functional changes. area/misc Impacts miscellaneous areas of the code not otherwise owned by another area. area/clustermesh Relates to multi-cluster routing functionality in Cilium. labels Jun 14, 2023
@giorio94 giorio94 requested review from a team as code owners June 14, 2023 10:28
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 14, 2023
@giorio94 giorio94 added release-note/misc This PR makes changes that have no direct user impact. and removed area/misc Impacts miscellaneous areas of the code not otherwise owned by another area. labels Jun 14, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 14, 2023
@giorio94
Copy link
Member Author

/test

Currently, the clustermesh-apiserver waits for the presence of all the
CRDs before starting the main logic, way more than the resource types
actually used afterwards. This ends up preventing the possibility of
running a newer version of the clustermesh-apiserver alongside older
versions of cilium/cilium-operator due to newly introduced CRDs.

This commit modifies the logic to only wait for the CRDs which are
actually used (the new list matches the entries listed in the
clustermesh-apiserver cluster role).

Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
@giorio94 giorio94 force-pushed the mio/clustermesh-apiserver-sync-crds branch from 534e081 to 74910f0 Compare June 14, 2023 11:51
@giorio94
Copy link
Member Author

/test

@giorio94
Copy link
Member Author

/ci-aks

@giorio94
Copy link
Member Author

/ci-awscni

@giorio94
Copy link
Member Author

Reviews from in, and tests are green. Marking as ready to merge

@giorio94 giorio94 added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 16, 2023
@sayboras sayboras merged commit 21b520e into cilium:main Jun 16, 2023
65 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clustermesh Relates to multi-cluster routing functionality in Cilium. kind/cleanup This includes no functional changes. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants