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

Cherry-pick #10476 to 6.7: Fix stopping of modules started by kubernetes autodiscover #10643

Merged
merged 1 commit into from
Feb 11, 2019

Commits on Feb 7, 2019

  1. Fix stopping of modules started by kubernetes autodiscover (elastic#1…

    …0476)
    
    Kubernetes autodiscover only emits events for containers with
    an ID in pods with an IP, but when a pod is being terminated,
    their containers can lack of ID and the pod itself can lack of IP.
    This leads to modules that are never stopped because the
    delete event that should stop them lacks of the needed
    information.
    
    This change makes two things to avoid this problem:
        * Don't require the pod to have an IP on stop events.
        * Use IDs for containers that don't depend on its state.
    
    (cherry picked from commit 15f2f26)
    jsoriano committed Feb 7, 2019
    Configuration menu
    Copy the full SHA
    f06a4e5 View commit details
    Browse the repository at this point in the history