Filter pod statuses reported back to containers which exist in proxy pod #206
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.
If extra containers are injected, the status for those containers is getting reported back into the proxy pod status.
This confuses or breaks clients reading pod status expecting every named container status to correlate to a named container in pod spec (for example, kubernetes/kubernetes#124906).
This PR prunes out container statuses for named containers which do not exist in the proxy pod.