-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Ensure that init containers are no longer tailed after they stop #14394
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Thanks @vjsamuel Can you add a changelog entry? |
90c2494
to
2adbe58
Compare
thanks @odacremolbap. I have done the needful. |
2adbe58
to
f3cfbd3
Compare
@vjsamuel sorry for the multi-step review. tests are failing because container status are not being informed at a "start" pod test. Adding
(note: that "v1" import at my example depends on goimports configured at my IDE, no need to change that) |
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 fix tests as depicted here?
f3cfbd3
to
d941fe4
Compare
@odacremolbap done. thanks for debugging the build failure. |
@vjsamuel LGTM |
…stic#14394) (cherry picked from commit aaca48b)
…stic#14394) (cherry picked from commit aaca48b)
…longer tailed after they stop (elastic#14476) * Ensure that init containers are no longer tailed after they stop (elastic#14394)
Init containers are killed off immediately after their work is done. So, ideally we should stop polling their endpoints and tailing their log files. The lack of this check impacted one of our builders that didnt have container in the log file path. Which caused the same path to be tailed multiple times.