kubernetes-client / java

Official Java client library for kubernetes
http://kubernetes.io/
Apache License 2.0
3.56k stars 1.9k forks source link

[documentation] Question on Compatibility matrix and Instructions for Maven/Gradle #1049

Closed ramanNarasimhan77 closed 3 years ago

ramanNarasimhan77 commented 4 years ago

Hello, I have a kubernetes environment with version 1.18.0. While running an application that uses kubernetes java client version 6.0.1, I faced some errors due to missing value for metadata.managedFields.fieldsType. I believe this is caused by using incorrect client version.

I am trying to figure out which kubernetes versions are compatible with k8s java client version 6.0.1 and which version to use with kubernetes 1.18.0 so that I can co-ordinate with the application developer and work on either getting the compatibility issue fixed or downgrade the kubernetes version on the cluster.

For this purpose, I tried checking the readme available for recent releases and have not been able to figure this out. Is there someplace that I can lookup to get the up-to-date dependency matrix and correct maven dependencies?

References

From The instructions given in readme in the tag client-java-parent-6.0.1

Maven version set as 5.0.0

image

Compatibility matrix

image

From instructions given in the tag client-java-parent-8.0.2

Maven dependency is still having version 5.0.0

image

Compatibility matrix is missing entries for 8.x client versions

image
brendandburns commented 4 years ago

You can find the matrix here: https://github.com/kubernetes-client/java#compatibility

8.0.2 corresponds to Kubernetes 1.16

We should probably cut a 9.x.y soon to provide 1.17 support (and eventually a 10.x.y after that with 1.18 support, or perhaps )

Regardless the library should work properly with 1.18 for most objects, it would only be alpha/beta objects where there are some problems.

I would definitely recommend the 8.0.2 library though it has a lot of bug fixes in addition to revised client code.

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

brendandburns commented 3 years ago

I'm closing this issue as I believe that the question has been resolved. Please use /reopen if you need further assistance on this issue.