Increase Kind apiserver event TTL from 1h to 4h#2351
Open
delthas wants to merge 1 commit intodevelopment/2.14from
Open
Increase Kind apiserver event TTL from 1h to 4h#2351delthas wants to merge 1 commit intodevelopment/2.14from
delthas wants to merge 1 commit intodevelopment/2.14from
Conversation
Kubernetes events expire after 1 hour by default. In CI, kind export logs often runs 1-2 hours after the test window, by which time the relevant events have already been garbage-collected. This was a concrete gap during the Azure archive flakiness investigation (PR #2340): the failing tests ran around 06:36 but kind export logs didn't execute until ~08:22 — nearly 2 hours later. All Kubernetes events from the failure window (pod scheduling, restarts, liveness probe failures, OOM kills) had expired and were unavailable for diagnosis. Bump --event-ttl to 4h via a kubeadm ClusterConfiguration patch in the Kind cluster config, ensuring events survive for the entire duration of CI jobs. Issue: ZENKO-5217
Contributor
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Contributor
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
SylvainSenechal
approved these changes
Mar 13, 2026
This file contains hidden or 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
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.
Summary
kube-apiserver --event-ttlfrom the default 1h to 4h in the Kind CI cluster configurationClusterConfigurationkubeadm patch inbootstrap-kind.shContext
During the investigation of Azure archive test flakiness (PR #2340, documented in ZENKO-5216), we found that Kubernetes events from the failure window were gone by the time artifacts were collected.
The failing archive tests ran around 06:36, but
kind export logsdidn't execute until ~08:22 — nearly 2 hours later. With the default 1-hour TTL, all events from the test window (pod scheduling, container restarts, liveness probe failures) had been garbage-collected by the apiserver. This left us unable to determine whether sorbet-fwd or sorbet-azure experienced restarts or probe failures during the critical window.Increasing the TTL to 4 hours ensures events survive for the full duration of any CI job, making them available in the
kind export logsoutput alongside the Fluent Bit persistent logs added in PR #2350.Issue: ZENKO-5217