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

DM-41630: Remove pod state tracking #221

Merged
merged 1 commit into from
Nov 7, 2023
Merged

DM-41630: Remove pod state tracking #221

merged 1 commit into from
Nov 7, 2023

Conversation

rra
Copy link
Member

@rra rra commented Nov 7, 2023

Previously, we attempted to track whether the pod for a user's lab was present. After some practical experience, this seems pointless. The important information is already captured in the lab state, and if we really want to know if the pod exists (it's mostly not clear that this matters), we can look directly in Kubernetes, since it would only be for debugging purposes. Drop this tracking.

Previously, we attempted to track whether the pod for a user's lab
was present. After some practical experience, this seems pointless.
The important information is already captured in the lab state, and
if we really want to know if the pod exists (it's mostly not clear
that this matters), we can look directly in Kubernetes, since it would
only be for debugging purposes. Drop this tracking.
@rra rra merged commit cc508f3 into main Nov 7, 2023
@rra rra deleted the tickets/DM-41630 branch November 7, 2023 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant