Skip to content
This repository has been archived by the owner on Dec 24, 2019. It is now read-only.

Handle pods with failed initcontainers or weird statuses #18

Merged
merged 2 commits into from
Jan 10, 2019
Merged

Handle pods with failed initcontainers or weird statuses #18

merged 2 commits into from
Jan 10, 2019

Conversation

aermakov-zalando
Copy link
Contributor

Handle initContainers as well to avoid issues with pods that don't have a started container.

Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
filter() returns a generator, not a list, so the next check will fail.

Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
@hjacobs
Copy link
Owner

hjacobs commented Jan 8, 2019

@aermakov-zalando is this still needed when we have zalando-incubator/kubernetes-on-aws#1668 ?

@aermakov-zalando
Copy link
Contributor Author

We don't know yet if the TTL controller actually works. Plus it could be useful for other users?

@hjacobs
Copy link
Owner

hjacobs commented Jan 9, 2019

@aermakov-zalando OK, is this PR code now the actually tested code (after the fix of the fix)? I'm referring to zalando-incubator/kubernetes-on-aws#1674

@aermakov-zalando
Copy link
Contributor Author

It ran on my machine. :) We'll roll out the fix to all clusters soon.

@hjacobs hjacobs merged commit b6c3c10 into hjacobs:master Jan 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants