Since the last summer changes where made to golang packages handling k8s api. If you kept your k8s.io/klog repo to master branch, then it was updated to klog v1.0.0. This breaks up building the go binary, especially in automated processes where pkgs get pulled every time.

I have found a workaround in this article:

In the client-go/go.mod file I have changed from k8s.io/klog v1.0.0 to k8s.io/klog v0.4.0

and then:

cd $GOPATH/src/k8s.io/klog git checkout v0.4.0

However I would like to now if there is a best practice around this, especially for CI/CD. I do not think that handling this issue manually is a graceful way.

Is it supposed to get fixed in the future?