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
pkg/k8s: decrease CEP status initialization #11829
Conversation
test-me-please |
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.
Can you revert #11771 as the part of this PR, and see whether we don't hit the flake anymore?
When an endpoint is created, its status is only created 10 seconds after. This happens because Kubernetes ignores the status field of a CRD object on its initialization and Cilium has a controller running every 10 seconds. In order to have a shorter CEP update window, Cilium can create the status field immediately after the creation of the CEP without waiting for the next execution of the CEP controller to be executed. Signed-off-by: André Martins <andre@cilium.io>
2b7f272
to
92a3948
Compare
Commit 92a3948fab08e7b84d207a4404eb071530041de6 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
This reverts commit 9accb13. Signed-off-by: André Martins <andre@cilium.io>
92a3948
to
f2c55c7
Compare
Commit 92a3948fab08e7b84d207a4404eb071530041de6 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
test-focus K8sServicesTest.*Tests NodePort with sessionAffinity from outside |
test-focus K8sServicesTest.* |
test-me-please |
test-focus K8sServicesTest.* (giving it more tries to ensure that the flake is gone) |
test-focus K8sServicesTest.* build aborted? https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated-Focus/229/execution/node/121/log/ |
test-focus K8sServicesTest.* Green |
1 similar comment
test-focus K8sServicesTest.* Green |
retest-net-next previous net-next failure https://jenkins.cilium.io/job/Cilium-PR-K8s-oldest-net-next/539/ |
retest-net-next previous net-next failure https://jenkins.cilium.io/job/Cilium-PR-K8s-oldest-net-next/572/ |
When an endpoint is created, its status is only created 10 seconds
after. This happens because Kubernetes ignores the status field of a CRD
object on its initialization and Cilium has a controller running every
10 seconds.
In order to have a shorter CEP update window, Cilium can create the
status field immediately after the creation of the CEP without waiting
for the next execution of the CEP controller to be executed.
Signed-off-by: André Martins andre@cilium.io
Fixes #11751