-
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
Update kopeio auth #3928
Update kopeio auth #3928
Conversation
/retest |
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.
You still owe docs on this. Please include something ... pretty please
Added docs for the kops side. It's still not really recommended... |
This is the last PR in the 1.8.0 milestone, other than nvme (still not clear what we should do) and other than the channel updates (which don't block a build). Then we can cut the next beta - I think we should but another beta given timings and the amount of churn since beta.1, along with the fact that k8s 1.8 still has that aggregated apiserver bug. I'm going to attack the 1.8.0 issue backlog next.... |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrislovecnm The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
No description provided.