Skip to content
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

add a pod list cache to continue tailing logs even if the API server or kubelet fails #37

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

sharkpc138
Copy link
Contributor

Previously, if there was an issue with the API server or kubelet and the pod list retrieval failed, the tailer was not added.

In this version, even if pod list retrieval fails, the previously cached pod list is utilized.
This ensures that a closed tailer in an idle state can also be tracked in the next loop using the cached pod list.

@sharkpc138 sharkpc138 force-pushed the add-customize_log_export_dir branch from 21bd66b to e53b379 Compare January 8, 2025 05:23
@sharkpc138 sharkpc138 force-pushed the add-customize_log_export_dir branch from e53b379 to 31d45f6 Compare January 8, 2025 05:29
@sharkpc138 sharkpc138 force-pushed the add-pod_info_cache branch 2 times, most recently from 4a7ebe2 to 68a10b0 Compare January 8, 2025 08:01
@sharkpc138 sharkpc138 force-pushed the add-customize_log_export_dir branch from d98e21d to 897d10c Compare January 9, 2025 01:16
@sharkpc138 sharkpc138 merged commit 40d0439 into add-customize_log_export_dir Jan 9, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant