Skip to content

Skip retrieving listeners for pods that have a deletionTimestamp to avoid deadlock waiting for secret operator pvcs when the listeners have already been garbage collected - #755

Open
soenkeliebau wants to merge 3 commits into
mainfrom
fix/720-skip-podlisteners
Open

soenkeliebau wants to merge 3 commits into
mainfrom
fix/720-skip-podlisteners

Conversation

@soenkeliebau

Copy link
Copy Markdown
Member

Description

fixes #720

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes

Author

  • Changes are OpenShift compatible
  • Helm chart can be installed and deployed operator works
  • Integration tests passed (for non trivial changes)
  • Changes need to be "offline" compatible

Reviewer

  • Code contains useful comments
  • Code contains useful logging statements
  • (Integration-)Test cases added
  • Documentation added or updated. Follows the style guide.
  • Changelog updated
  • Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

  • Feature Tracker has been updated
  • Proper release label has been added
  • Links to generated (nightly) docs added
  • Release note snippet added
  • Add type/deprecation label & add to the deprecation schedule
  • Add type/experimental label & add to the experimental features tracker

…void deadlock waiting for secret operator pvcs when the listeners have already been garbage collected.

#720
@soenkeliebau
soenkeliebau requested a review from a team September 11, 2026 08:30
Comment on lines +243 to +251
let is_being_deleted = pod.metadata.deletion_timestamp.is_some();
let pod_info = SchedulingPodInfo::from_pod(
&self.client,
&pod,
&selector.scope,
is_being_deleted,
)
.await
.context(ParsePodSnafu)?;

@NickLarsenNZ NickLarsenNZ Sep 14, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

&pod is already given to from_pod as an argument. So I don't think there is a need to pass an extra argument.

The deletion_timestamp check can be done inside that function.

@NickLarsenNZ NickLarsenNZ moved this to Development: In Review in Stackable Engineering Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: In Review

Development

Successfully merging this pull request may close these issues.

skip the PodListeners lookup when the served Pod is being deleted

2 participants