chore(ci): Re-update k8s-e2e to use new helm chart #10567
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jszwedko
added
ci-condition: k8s e2e all targets
|
✔️ Deploy Preview for vector-project canceled. 🔨 Explore the source changes: da7888f 🔍 Inspect the deploy log: https://app.netlify.com/sites/vector-project/deploys/61ca15462b04210008649609 |
github-actions
bot
added
the
domain: ci
Soak Test ResultsBaseline: 738e6c2 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. Test units below are bytes/second/CPU, except for "skewness". The further "skewness" is from 0.0 the more indication that vector lacks consistency in behavior, making predictions of fitness in the field challenging. The abbreviated 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. 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. The abbreviated table will be omitted if no statistically interesting changes are observed. No statistically interesting changes with confidence 90.00%. Fine details of change detection per experiment.
Fine details of each soak run.
|
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
Soak Test ResultsBaseline: 8ab99d1 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. Test units below are bytes/second/CPU, except for "skewness". The further "skewness" is from 0.0 the more indication that vector lacks consistency in behavior, making predictions of fitness in the field challenging. The abbreviated 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. 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. The abbreviated table will be omitted if no statistically interesting changes are observed. No statistically interesting changes with confidence 90.00%. Fine details of change detection per experiment.
Fine details of each soak run.
|
spencergilbert
force-pushed
the
revert-10566-revert-10521-spencer/10467-update-k8s-e2e-to-new-helm
branch
from
2ac0bc1 to
c325b36
Compare
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
spencergilbert
force-pushed
the
revert-10566-revert-10521-spencer/10467-update-k8s-e2e-to-new-helm
branch
from
c325b36 to
1dacc57
Compare
Soak Test ResultsBaseline: 2400b48 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. Test units below are bytes/second/CPU, except for "skewness". The further "skewness" is from 0.0 the more indication that vector lacks consistency in behavior, making predictions of fitness in the field challenging. The abbreviated 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. 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. The abbreviated table will be omitted if no statistically interesting changes are observed. No statistically interesting changes with confidence 90.00%. Fine details of change detection per experiment.
Fine details of each soak run.
|
|
Upgrading runner@fv-az201-838:~/work/vector/vector$ kubectl get all -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system pod/coredns-f9fd979d6-4r8wf 0/1 ContainerCreating 0 7m55s
...
kube-system pod/kube-proxy-7ms4g 0/1 CreateContainerError 0 7m55s
...
kube-system pod/storage-provisioner 0/1 CrashLoopBackOff 5 8m8sSeemingly related: kubernetes/minikube#12684 kubernetes/minikube#12705 kubernetes-sigs/kind#2058 However it does seem like the underlying versions are new enough that they should be patched, unless I'm missing something: docker@minikube:~$ sudo runc --version
runc version 1.0.1
commit: v1.0.1-0-g4144b63
spec: 1.0.2-dev
go: go1.15.14
libseccomp: 2.5.1
docker@minikube:~$ sudo crictl version
Version: 0.1.0
RuntimeName: cri-o
RuntimeVersion: 1.22.0
RuntimeApiVersion: v1alpha2 |
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
Soak Test ResultsBaseline: 2400b48 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. Test units below are bytes/second/CPU, except for "skewness". The further "skewness" is from 0.0 the more indication that vector lacks consistency in behavior, making predictions of fitness in the field challenging. The abbreviated 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. 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. The abbreviated table will be omitted if no statistically interesting changes are observed.
Fine details of change detection per experiment.
Fine details of each soak run.
|
jszwedko
added a commit
that referenced
this pull request
Dec 27, 2021
Isolating from #10567 Signed-off-by: Jesse Szwedko <jesse@szwedko.me>
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
Soak Test ResultsBaseline: e3dd70e 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. Test units below are bytes/second/CPU, except for "skewness". The further "skewness" is from 0.0 the more indication that vector lacks consistency in behavior, making predictions of fitness in the field challenging. The abbreviated 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. 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. The abbreviated table will be omitted if no statistically interesting changes are observed. No statistically interesting changes with confidence 90.00%. Fine details of change detection per experiment.
Fine details of each soak run.
|
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
Soak Test ResultsBaseline: f228891 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. Test units below are bytes/second/CPU, except for "skewness". The further "skewness" is from 0.0 the more indication that vector lacks consistency in behavior, making predictions of fitness in the field challenging. The abbreviated 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. 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. The abbreviated table will be omitted if no statistically interesting changes are observed. No statistically interesting changes with confidence 90.00%. Fine details of change detection per experiment.
Fine details of each soak run.
|
jszwedko
commented
Dec 28, 2021
jszwedko
deleted the
revert-10566-revert-10521-spencer/10467-update-k8s-e2e-to-new-helm
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #10566
Re-introduces for debugging.