-
Notifications
You must be signed in to change notification settings - Fork 1.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
fix(kubernetes_logs): Compile kube-rs with openssl #13038
fix(kubernetes_logs): Compile kube-rs with openssl #13038
Conversation
This is to avoid breaking kubernetes_source inside clusters with k3s. For more info check the issue kube-rs/kube#805
✅ Deploy Preview for vector-project canceled.
|
Signed-off-by: Spencer Gilbert <[email protected]>
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.
Thanks @jaysonsantos ! The e2e k8s tests look good.
Soak Test ResultsBaseline: 1ba91c9 ExplanationA soak test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine, quickly, if vector performance is changed and to what degree by a pull request. Where appropriate units are scaled per-core. The table below, if present, lists those experiments that have experienced a statistically significant change in their throughput performance between baseline and comparision SHAs, with 90.0% confidence OR have been detected as newly erratic. Negative values mean that baseline is faster, positive comparison. Results that do not exhibit more than a ±8.87% change in mean throughput are discarded. An experiment is erratic if its coefficient of variation is greater than 0.3. The abbreviated table will be omitted if no interesting changes are observed. No interesting changes in throughput with confidence ≥ 90.00% and absolute Δ mean >= ±8.87%: Fine details of change detection per experiment.
|
Soak Test ResultsBaseline: 1ba91c9 ExplanationA soak test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine, quickly, if vector performance is changed and to what degree by a pull request. Where appropriate units are scaled per-core. The table below, if present, lists those experiments that have experienced a statistically significant change in their throughput performance between baseline and comparision SHAs, with 90.0% confidence OR have been detected as newly erratic. Negative values mean that baseline is faster, positive comparison. Results that do not exhibit more than a ±8.87% change in mean throughput are discarded. An experiment is erratic if its coefficient of variation is greater than 0.3. The abbreviated table will be omitted if no interesting changes are observed. No interesting changes in throughput with confidence ≥ 90.00% and absolute Δ mean >= ±8.87%: Fine details of change detection per experiment.
|
* fix(kubernetes_logs): Compile kube-rs with openssl This is to avoid breaking kubernetes_source inside clusters with k3s. For more info check the issue kube-rs/kube#805 * +e2e ci Signed-off-by: Spencer Gilbert <[email protected]> Co-authored-by: Spencer Gilbert <[email protected]>
* fix(kubernetes_logs): Compile kube-rs with openssl This is to avoid breaking kubernetes_source inside clusters with k3s. For more info check the issue kube-rs/kube#805 * +e2e ci Signed-off-by: Spencer Gilbert <[email protected]> Co-authored-by: Spencer Gilbert <[email protected]>
* fix(kubernetes_logs): Compile kube-rs with openssl This is to avoid breaking kubernetes_source inside clusters with k3s. For more info check the issue kube-rs/kube#805 * +e2e ci Signed-off-by: Spencer Gilbert <[email protected]> Co-authored-by: Spencer Gilbert <[email protected]>
This is to avoid breaking kubernetes_source inside clusters with k3s.
For more info check the issue kube-rs/kube#805
This fixes #12989