-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Change dependency management from godep to dep #3037
Comments
Looks like some issue when doing
|
After creating the vendor directory from the
|
it could be they apply fixes on top of the vendor. might this be the cause
of this?
|
It is because dep isn't able to pick up the internal dependencies of k8s.io/client-go. You need to explicitly pin the correct versions of k8s.io/api and k8s.io/apimachinery in Gopkg.toml. For example, [[constraint]]
name = "k8s.io/api"
version = "kubernetes-1.11.x"
[[constraint]]
name = "k8s.io/apimachinery"
version = "kubernetes-1.11.x"
[[constraint]]
name = "k8s.io/client-go"
version = "8.0.0" Depending on your version of k8s.io/client-go, the version of the other two will change. |
@jlnaps I will try that also and let you know. By any chance if you are able to do it successfully can you send PR? |
@praveenkumar I don't think it is something I can generate a PR for, as everyone's Gopkg.toml will be different, but if you paste the following: [[constraint]]
name = "k8s.io/api"
version = "kubernetes-1.11.2"
[[constraint]]
name = "k8s.io/apimachinery"
version = "kubernetes-1.11.2"
[[constraint]]
name = "k8s.io/client-go"
version = "8.0.0" and do a dep ensure, things should build as normal. Those are the current 1.11.x versions at this time, so if anyone plugging the error into Google finds this(this thread is the top hit as of last week), they may be different. |
@jlnaps just wanted to say thanks for your reply. I came here from the top result of Google and was able to get working on 1.10 cluster with the following:
|
I think we should change to dep. I tried once and got stuck, but I'll happily take a PR that gets us there :) |
Awesome. @praveenkumar and I spoke recently with @balopat and agreed godep
for now is the way to go. Although 1.11 will offer vgo, it would be too
early to adapt this... and aligning between minishift and minikube at this
stage is more important.
|
0.29.0 Release * tag 'v0.29.0': (77 commits) Cut release 0.29.0 (kubernetes#3175) turning error into a warning log message Bump everything to 1.11. Update docs. Update go-ansiterm. Issue kubernetes#3037 change dependency management to dep inlining deleteNetwork into if statement update dashboard version Fix typo: suppports -> supports adding tstromberg kvm2 driver: fixed documentation link in error text kvm2 driver: be more robust with creating of the network, don't delete the network if it is in use kvm2 driver: generate separate random MACs for default and private network NICs kvm2 driver: separated activating and creating of networks kvm2 driver: fixed private network creation and setup fix: --format outputs any string, --https only subsitute http URL scheme Stay in same line Change default docker storage driver to overlay2 Simplifies Linux installation instructions by using install(1) update ...
For some stupid reason, they have to be pinned together. See kubernetes/minikube#3037 and https://github.com/kubernetes/client-go#compatibility-matrix
* Update client-go * Bump all k8s libs in tandem For some stupid reason, they have to be pinned together. See kubernetes/minikube#3037 and https://github.com/kubernetes/client-go#compatibility-matrix
Looks like we are still using
godep
which is way older and not in active maintenance. I think we should switch to dep which right now in active development and maintenance.The text was updated successfully, but these errors were encountered: