Re: [kubernetes/kubernetes] Use multihosts feature from client-go (#40674)
Mike Danese
This also has some api changes in clientcmd api group @kubernetes/sig-api-machinery-api-reviews
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Andreas Tsaridas
ping @dshulyak
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Joshua Dotson
/remove-lifecycle stale
cmluciano
ping @dshulyak ^
krmayankk
@dshulyak are you still working on this , i can work on this if no one has picked it up
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
Avi Deitcher
/remove-lifecycle stale
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Avi Deitcher
/remove-lifecycle rotten
Jordan Liggitt
Closing for lack of activity. If there is interest in pursuing this, this seems like a fundamental enough change to warrant a KEP.
/close
Kubernetes Prow Robot
@liggitt: Closed this PR.
In response to this:
Closing for lack of activity. If there is interest in pursuing this, this seems like a fundamental enough change to warrant a KEP.
/close
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.
Kubernetes Prow Robot
Closed #40674.
agile6v
/reopen
We really need this feature. Hope it could continue.
Thanks.
Kubernetes Prow Robot
@agile6v: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
We really need this feature. Hope it could continue.
Thanks.
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.
—
agile6v
/reopen
We really need this feature. Hope it could continue.
Thanks.
Hello @hzxuzhonghu @dshulyak @brendandburns
How to reopen it ?
Thanks.
Zhonghu Xu
I think only the author and k8s collaborator can reopen.