-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Repick upstream commits for publisher bot #21921
Conversation
/cc @smarterclayton |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mfojtik, soltysh 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
…endpoint Provide an administrator a streaming view of journal logs without them having to implement a client side reader. Only available to cluster admins.
…y-run This is fixed in 1.12 so the commit can safely be dropped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/retest |
1 similar comment
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
Bump all dependencies and re-pick commits so the publisher bots can apply them to forks.
This is needed because the publish bot use the rebase commit as base for syncing. However it won't pick commits in the same PR (rebase) branch...
Pinned
github.com/gorilla/mux
andgithub.com/ghodss/yaml
to kube 1.12 levels as it got bumped to levels that require plumbing in kubernetes code.