fix(native): honor system namespace in list workloads#514
Merged
jordan-rash merged 1 commit intomainfrom Apr 9, 2026
Merged
Conversation
The native nexlet's GetNamespaceWorkloadList did a flat map lookup and did not honor the system namespace convention, so a system-user list returned nothing from user namespaces. It also silently dropped the filter argument, and WorkloadSummary had no way to report which namespace a workload actually lived in. - Add an optional namespace field to WorkloadSummary - Native and in-mem nexlets return workloads across every namespace when queried with the system namespace - Wire the filter argument through native and match against both workload id and workload name; in-mem now matches on name too. Signed-off-by: Jordan Rash <jordan@synadia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The native nexlet's GetNamespaceWorkloadList did a flat map lookup and did not honor the system namespace convention, so a system-user list returned nothing from user namespaces. It also silently dropped the filter argument, and WorkloadSummary had no way to report which namespace a workload actually lived in.