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#40

Merged
abhinavdahiya merged 2 commits into
release-1.22.9-lyft.5from
non-sidecar-empty
Jun 22, 2023
Merged

containers should always be allowed to start when no sidecar is present#40
abhinavdahiya merged 2 commits into
release-1.22.9-lyft.5from
non-sidecar-empty

Conversation

@abhinavdahiya
Copy link
Copy Markdown

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.

@abhinavdahiya
Copy link
Copy Markdown
Author

ptal #compute @tomwans

Comment thread pkg/kubelet/status/status_manager.go Outdated
Comment thread pkg/kubelet/status/status_manager.go Outdated
Co-authored-by: Tom Wanielista <tomwans@users.noreply.github.com>
@abhinavdahiya abhinavdahiya changed the base branch from release-1.22.9-lyft.4 to release-1.22.9-lyft.5 June 22, 2023 19:18
@abhinavdahiya abhinavdahiya merged commit 49b8055 into release-1.22.9-lyft.5 Jun 22, 2023
@abhinavdahiya abhinavdahiya deleted the non-sidecar-empty branch June 22, 2023 19:18
abhinavdahiya added a commit that referenced this pull request Jun 22, 2023
…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 added a commit that referenced this pull request Jun 22, 2023
…nt (#41)

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.

Co-authored-by: Tom Wanielista <tomwans@users.noreply.github.com>
abhinavdahiya added a commit that referenced this pull request Jun 26, 2023
…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 added a commit that referenced this pull request Jun 26, 2023
…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 added a commit that referenced this pull request Jul 28, 2023
…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 added a commit that referenced this pull request Aug 9, 2023
…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 added a commit that referenced this pull request Aug 10, 2023
…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 added a commit that referenced this pull request Nov 29, 2023
…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 added a commit that referenced this pull request Nov 29, 2023
…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 added a commit that referenced this pull request Dec 1, 2023
…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>
murongl-lyft pushed a commit that referenced this pull request Mar 8, 2024
…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>
murongl-lyft pushed a commit that referenced this pull request Mar 22, 2024
…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>
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