Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test pull-kops-e2e-k8s-aws-amazonvpc The other two look like a bug (we should never segfault!). I'll see if I can understand why we are segfaulting! |
50d7090 to
d9f6b79
Compare
|
The bare-metal flakes should be fixed by #18072 (which has merged, so you need to rebase because that is a Github Action test) |
| restConfig.UserAgent = "kops" | ||
| restConfig.Burst = 50 | ||
| restConfig.QPS = 20 | ||
| restConfig.AcceptContentTypes = runtime.ContentTypeProtobuf |
There was a problem hiding this comment.
Not a blocker, but should we specify a list (e.g. proto then json)? I thought the server was only allowed to send a type that was in the Accept header?
There was a problem hiding this comment.
I would expect it would be more compliant with HTTP standard, however it will work with K8s API Server as it will fallback itself to JSON.
|
/retest |
Experimenting with fixing
kops validate cluster --waitnot working for large cluster #18065First rule of K8s, always use protobuf