-
Notifications
You must be signed in to change notification settings - Fork 546
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
update vendored k8s to 1.11.3 #328
Conversation
Codecov Report
@@ Coverage Diff @@
## master #328 +/- ##
======================================
Coverage 50.5% 50.5%
======================================
Files 68 68
Lines 3188 3188
======================================
Hits 1610 1610
Misses 1317 1317
Partials 261 261 Continue to review full report at Codecov.
|
Updating vendored k8s here to 0.11.3 allows knative/build-pipeline to use the k8schain library, resolving this issue:
which is due to:
|
Is this because build-pipeline is using 1.11.3? Are we going to require all of our consumers to be on the same version? I wonder if the |
it seems knative/pkg vendors also vendors 0.11.3 so it might be worth trying to update as there might be more issues in trying to use the kubeclient as a param in the libs together. When I updated knative/build-pipeline to to use my fork of go-containerregistry which has this updated there are new errors related the the Azure packages k8schain vendors. Edit: My current plan is to have build-pipeline (at least as I'm trying to get things tested/working) use a kubeclient from the vendored kube lib. |
cc @mattmoor |
@jonjohnsonjr yes, currently build-pipeline uses 0.11.3 |
Can you paste the errors you get when you try to use your fork? |
Errors using my fork w/ the updated k8s version:
I have tried tweaking the versions of azure-sdk-for-go but have so far always ended up with some set of errors. |
I was able to resolve the issues I was having with my fork. I pinned a different version of azure and changed the import paths of my fork to "aaron-prindle/go-containerregistry". |
Can you pin that version in this PR? |
I actually pinned the version in go-containerregistry to be used in knative/build-pipeline and that resolved it. The versions here should work w/o change. |
No description provided.