-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
✨ Bump k8s deps to 1.26.10 #2559
✨ Bump k8s deps to 1.26.10 #2559
Conversation
Bump k8s deps to 1.26.10 to include fixes for CVE-2023-39325. Signed-off-by: Varsha Prasad Narsing <varshaprasad96@gmail.com>
The test seems to be passing locally:
/test pull-controller-runtime-test-release-0-14 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer, varshaprasad96 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 |
Aligned with kubernetes-sigs/controller-runtime#2559 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
#2896) * 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> * Bump k8s deps to 1.26.10 Aligned with kubernetes-sigs/controller-runtime#2559 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> --------- Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
Aligned with kubernetes-sigs/controller-runtime#2559 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
Aligned with kubernetes-sigs/controller-runtime#2559 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
…g to wrong mapper (#2977) * 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> * Bump k8s deps to 1.26.10 Aligned with kubernetes-sigs/controller-runtime#2559 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> --------- Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> Co-authored-by: Alex Kalenyuk <akalenyu@redhat.com>
…g to wrong mapper (#2978) * 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> * Bump k8s deps to 1.26.10 Aligned with kubernetes-sigs/controller-runtime#2559 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com> --------- Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
Bump k8s deps to 1.26.10 to include fixes for
CVE-2023-39325.