Package upgrade blocked

[regnaio]

Please refer to the command and its output below:

go get -u ./...

# k8s.io/client-go/applyconfigurations/meta/v1
/go/pkg/mod/k8s.io/client-go@v0.23.5/applyconfigurations/meta/v1/unstructured.go:64:37: cannot use doc (type *"github.com/googleapis/gnostic/openapiv2".Document) as type *"github.com/google/gnostic/openapiv2".Document in argument to "k8s.io/kube-openapi/pkg/util/proto".NewOpenAPIData

[zrks]

just stumbled upon same issue :/

[toms-place]

Same here, but I think it already got resolved in an upcoming version:

Here the correct pkg gets imported: https://github.com/kubernetes/client-go/blob/v0.24.0-alpha.4/discovery/discovery_client.go#L32

[Dudssource]

Same problem here, updating all deps through go get -u doesn't work.

[zrks]

Same problem here, updating all deps through go get -u doesn't work.

update to v0.24.0-alpha.4, it helped me

[Dudssource]

Same problem here, updating all deps through go get -u doesn't work.

update to v0.24.0-alpha.4, it helped me

It worked @zrks ! Thank you!

[sumithreddy]

did anyone figure out a solution for this one. Looks like issue is on all versions of 0.23 other than upgrading to latest version

[nicks]

i was able to fix this by replacing the k8s.io/kube-openapi entry in the go.mod in my project with this:

k8s.io/kube-openapi v0.0.0-20211115234752-e816edb12b65 // indirect

[jbyers19]

Adding this to my go.mod fixed some of the openapi type errors I was running into:

replace (
    github.com/googleapis/gnostic => github.com/googleapis/gnostic v0.5.5
)

[Jefftree]

The latest version of kube-openapi is only compatible with v0.24 of kubernetes so a go get -u on a v0.23 repo will pull in an incompatible module. I was under the impression that for a specific k8s release, we have dependencies pinned for a reason. Is it convention to run a go get -u on the client-go repo?

We try to maintain backwards incompatibility as much as possible, but things like module renames will cause version incompatibilities between certain versions.

cc @liggitt

[liggitt]

Is it convention to run a go get -u on the client-go repo?

no, upgrading to HEAD of all dependencies of client-go is not expected to work as long as some are on v0... revisions