Skip to content

Added pod data to endpoint query to know out which Pods are related #411

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.

Sign up for GitHub

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

Open
willianbriotto wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −0
Open

Added pod data to endpoint query to know out which Pods are related #411

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a91e713
Added pod data to endpoint query to know out which Pods are related t…
willianbriotto Apr 21, 2025
0080060
Merge branch 'main' into endpoints_pods
deanq Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions runpod/api/queries/endpoints.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,12 @@
id
dataCenterId
}
pods {
id
podType
ports
desiredStatus
}
Comment on lines +33 to +38
Copy link

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

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

Adding pods to the default QUERY_ENDPOINT means every get_endpoints() call will now fetch per-endpoint pod lists (and their ports/status), which can significantly increase response size and latency for users with many endpoints/pods. Consider keeping QUERY_ENDPOINT as a lightweight list query and introducing a separate/opt-in query (or a second constant like QUERY_ENDPOINT_WITH_PODS) for callers that actually need pod details.

Copilot uses AI. Check for mistakes.
}
}
}
Expand Down