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.

Sign up for GitHub

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

Jump to bottom

Bump controller runtime to avoid mistakenly defaulting to wrong mapper #2896

Merged
merged 2 commits into from
Nov 9, 2023
Merged

Bump controller runtime to avoid mistakenly defaulting to wrong mapper #2896

merged 2 commits into from
Nov 9, 2023

Commits on Oct 29, 2023

  1. Bump controller runtime to avoid mistakenly defaulting to wrong mapper 

    Today, controller runtime mistakenly ignores the inherited Manager default
dynamic mapper and uses a discovery mapper instead:
kubernetes-sigs/controller-runtime#2491
This means that if some CRD was not available on the cdi-controller startup,
Even if it got installed after, we would still get IsNoMatch when trying to access it.

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
    @akalenyu
    akalenyu committed Oct 29, 2023
    Configuration menu
    Copy the full SHA
    2edc9a9 View commit details
    Browse the repository at this point in the history

  2. Bump k8s deps to 1.26.10 

    Aligned with kubernetes-sigs/controller-runtime#2559

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
    @akalenyu
    akalenyu committed Oct 29, 2023
    Configuration menu
    Copy the full SHA
    8758826 View commit details
    Browse the repository at this point in the history