-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
[Flaking Test] integration TestEncryptionConfigHotReload #121313
Labels
kind/flake
Categorizes issue or PR as related to a flaky test.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Oct 18, 2023
/triage accepted |
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Oct 18, 2023
/cc @kubernetes/ci-signal |
@enj: Reopened this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/flake
Categorizes issue or PR as related to a flaky test.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Which jobs are flaking?
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-integration-master/1714423851380641792
k8s.io/kubernetes/test/integration/controlplane: transformation expand_less | 14m1s
Which tests are flaking?
TestEncryptionConfigHotReload
Since when has it been flaking?
When I see this flake, 10-09 is the first one.(But the job history in the testgrid only started from 10-03)
Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#integration-master
Reason for failure (if possible)
Anything else we need to know?
some PR that may be related: #120544
Relevant SIG(s)
/sig auth
/cc @ritazh
The text was updated successfully, but these errors were encountered: