You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
arquillian-cube:1.18.3-SNAPSHOT was using io.fabric8::4.0.3.
Package names in version 4.0.3 all had names containing the string
"v4_0". (e.g. io.fabric8.kubernetes.api.model.v4_0.Namespace)
io.fabric8::5.x.x is mostly 4.0.3 code with "v4_0" removed
from the package names. There are a few classes with code changes
to be considered. io.fabric8:*:6.x.x has significant code changes.
So much so that a migrations guide has been provided. https://github.com/fabric8io/kubernetes-client/blob/main/doc/MIGRATION-v6.md
Upgrading to io.fabric8:6.9.2 will required extensive evaluation and changes
to code in module kubernetes.kubernetes.
Here is the list of io.fabric8 archives arquillian-cube references.
io.fabric8:kubernetes-openshift-uberjar
io.fabric8:kubernetes-client
io.fabric8:openshift-client
io.fabric8:kubernetes-client-api
This issue depends on #1270
being resolved first.
See tracker doc, #1279
The text was updated successfully, but these errors were encountered:
arquillian-cube:1.18.3-SNAPSHOT was using io.fabric8::4.0.3.
Package names in version 4.0.3 all had names containing the string
"v4_0". (e.g. io.fabric8.kubernetes.api.model.v4_0.Namespace)
io.fabric8::5.x.x is mostly 4.0.3 code with "v4_0" removed
from the package names. There are a few classes with code changes
to be considered. io.fabric8:*:6.x.x has significant code changes.
So much so that a migrations guide has been provided.
https://github.com/fabric8io/kubernetes-client/blob/main/doc/MIGRATION-v6.md
Upgrading to io.fabric8:6.9.2 will required extensive evaluation and changes
to code in module kubernetes.kubernetes.
Here is the list of io.fabric8 archives arquillian-cube references.
io.fabric8:kubernetes-openshift-uberjar
io.fabric8:kubernetes-client
io.fabric8:openshift-client
io.fabric8:kubernetes-client-api
This issue depends on #1270
being resolved first.
See tracker doc, #1279
The text was updated successfully, but these errors were encountered: