-
Notifications
You must be signed in to change notification settings - Fork 40.6k
Plumb token and token file through rest.Config #71713
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
Conversation
/priority important-soon |
This is beautiful. |
debc6db
to
7c6a37c
Compare
@kubernetes/sig-cluster-lifecycle |
7c6a37c
to
aaed911
Compare
aaed911
to
db6e1c5
Compare
After seeing this I think clientcert should be handled the same way and we
should move the ugly transport.go hack in kubelet for cert rotation into
this mechanism. I see no reason why they aren't the same code. I will
take ownership of doing that follow up after this.
…On Tue, Dec 4, 2018 at 12:04 PM Kubernetes Prow Robot < ***@***.***> wrote:
@liggitt <https://github.com/liggitt>: The following tests *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-e2e-gce debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-e2e-gce/61820/> /test
pull-kubernetes-e2e-gce
pull-kubernetes-e2e-gce-device-plugin-gpu debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-e2e-gce-device-plugin-gpu/54717/> /test
pull-kubernetes-e2e-gce-device-plugin-gpu
pull-kubernetes-e2e-kops-aws debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-e2e-kops-aws/115763/> /test
pull-kubernetes-e2e-kops-aws
pull-kubernetes-node-e2e debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-node-e2e/113208/> /test
pull-kubernetes-node-e2e
pull-kubernetes-bazel-test debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-bazel-test/69393/> /test
pull-kubernetes-bazel-test
pull-kubernetes-e2e-gce-100-performance debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-e2e-gce-100-performance/28694/> /test
pull-kubernetes-e2e-gce-100-performance
pull-kubernetes-kubemark-e2e-gce-big debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-kubemark-e2e-gce-big/31154/> /test
pull-kubernetes-kubemark-e2e-gce-big
pull-kubernetes-local-e2e-containerized debc6db
<debc6db>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-local-e2e-containerized/3753/> /test
pull-kubernetes-local-e2e-containerized
pull-kubernetes-integration db6e1c5
<db6e1c5>
link
<https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71713/pull-kubernetes-integration/37538/> /test
pull-kubernetes-integration
Full PR test history <https://gubernator.k8s.io/pr/71713>. Your PR
dashboard <https://gubernator.k8s.io/pr/liggitt>. Please help us cut down
on flakes by linking to
<https://git.k8s.io/community/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#71713 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p34R7oaod5JgetEISdpx2aHAQkw7ks5u1qsUgaJpZM4ZBBt0>
.
|
/retest |
candidate for picking to 1.13 for client-go consumers |
@liggitt: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
db6e1c5
to
dba85e5
Compare
This packages are very non-idiomatic go ;( /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, mikedanese The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
xref #69234
alternative to #69272
Does this PR introduce a user-facing change?:
/assign @smarterclayton @mikedanese
/sig api-machinery
/sig auth