-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Spring Boot 3.5 + Spring Cloud 2025.0.0 Jackson 2.19 issue #7106
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
Comments
We have made the call to upgrade to 7.3.1 even though this is a breaking change for us it seems like the best option moving forward spring-cloud/spring-cloud-kubernetes#1923. We can close this issue for now. |
Nice, thx. |
The kubernetes client has issues with Jackson 2.19.0. Original pull request that updated to 2.19.0 was: * jenkinsci#10677 Reverted from the Jenkins plugin BOM in pull request: * jenkinsci/bom#5114 Distribution suspended from Jenkins update center in: * jenkins-infra/update-center2#869 Refer to the following Kubernetes client API issues: * fabric8io/kubernetes-client#7036 * fabric8io/kubernetes-client#7106 Backport of the Jackson 2.19.0 change to Kubernetes client 6.x has been requested at: * fabric8io/kubernetes-client#7107 Also described in detail in Spring Cloud issue report: * spring-cloud/spring-cloud-kubernetes#1923 Also described in Jenkins issue report: * https://issues.jenkins.io/browse/JENKINS-75712 Also verified as failing in kubernetes plugin pull request: * jenkinsci/kubernetes-plugin#1702 Also mentioned in Kubernetes client API upgrade pull request: * jenkinsci/kubernetes-client-api-plugin#292 This reverts commit 11e5d5c.
The kubernetes client has issues with Jackson 2.19.0. Original pull request that updated to 2.19.0 was: * #10677 Reverted from the Jenkins plugin BOM in pull request: * jenkinsci/bom#5114 Distribution suspended from Jenkins update center in: * jenkins-infra/update-center2#869 Refer to the following Kubernetes client API issues: * fabric8io/kubernetes-client#7036 * fabric8io/kubernetes-client#7106 Backport of the Jackson 2.19.0 change to Kubernetes client 6.x has been requested at: * fabric8io/kubernetes-client#7107 Also described in detail in Spring Cloud issue report: * spring-cloud/spring-cloud-kubernetes#1923 Also described in Jenkins issue report: * https://issues.jenkins.io/browse/JENKINS-75712 Also verified as failing in kubernetes plugin pull request: * jenkinsci/kubernetes-plugin#1702 Also mentioned in Kubernetes client API upgrade pull request: * jenkinsci/kubernetes-client-api-plugin#292 This reverts commit 11e5d5c.
Describe the bug
Generally identical to #7036, but in a different context.
Spring Boot 3.5 was released with a dependency on Jackson 2.19.0.
Spring Boot 3.5 is compatible with Spring Cloud 2025.0.0 only.
Spring Cloud 2025.0.0 depends on fabric8 kubernetes client 6.x and does not plan on moving to 7.x until Spring Boot 4.0.0 and Spring Cloud 2025.1.0. Effectively this would mean that this bug would be triggered.
I'm not a Spring/VMWare/Broadcom developer so I cannot predict what their intent is here, but it would make sense to me that they would want to see this fixed in Fabric8 Kubernetes Client 6.x so they don't have to deal with imposing any breaking changes on their users in a non-major release.
Fabric8 Kubernetes Client version
7.3.1
Steps to reproduce
Expected behavior
No NPE
Runtime
Kubernetes (vanilla)
Kubernetes API Server version
1.33
Environment
GKE
Fabric8 Kubernetes Client Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: