Skip to content
This repository was archived by the owner on Apr 20, 2026. It is now read-only.

containers should always be allowed to start when no sidecar is present#41

Merged
abhinavdahiya merged 1 commit into
release-1.16.15-lyft.5from
non-sidecar-empty-166
Jun 22, 2023
Merged

containers should always be allowed to start when no sidecar is present#41
abhinavdahiya merged 1 commit into
release-1.16.15-lyft.5from
non-sidecar-empty-166

Conversation

@abhinavdahiya
Copy link
Copy Markdown

Backport (#40)

based on
https://lyft.slack.com/archives/C017X524VC7/p1685639606706689?thread_ts=1685481685.730389&cid=C017X524VC7

when there are no sidecars we should allow all containers to start even when there is lack of container status.
This fixes a regression introduced in
#37 where we would block starting containers until we get container status reported. this triggers KillPod action in 1.16 as no progress can be made.

…nt (#40)

based on
https://lyft.slack.com/archives/C017X524VC7/p1685639606706689?thread_ts=1685481685.730389&cid=C017X524VC7

when there are no sidecars we should allow all containers to start even
when there is lack of container status.
This fixes a regression introduced in
#37 where we would block starting
containers until we get container status reported. this triggers KillPod
action in 1.16 as no progress can be made.

---------

Co-authored-by: Tom Wanielista <tomwans@users.noreply.github.com>
@abhinavdahiya abhinavdahiya changed the base branch from release-1.16.15-lyft.4 to release-1.16.15-lyft.5 June 22, 2023 20:19
@abhinavdahiya abhinavdahiya merged commit c54230f into release-1.16.15-lyft.5 Jun 22, 2023
@abhinavdahiya abhinavdahiya deleted the non-sidecar-empty-166 branch June 22, 2023 20:19
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.

3 participants