This is done by introducing a new common QueryBackendOptions struct which
contains all configuration information necessary to select the correct
backend to execute API queries against. The new TUI options embeds this
struct just like all other commands, and core query logic has been
updated to use QueryBackendOptions.
Does this PR rely on any other PRs?
N/A
How does this PR impact users? (This is the kind of thing that goes in release notes!)
kubectl cost tui supports the --kubecost-namespace and --service-name flags.
Links to Issues or ZD tickets this PR addresses or fixes
What does this PR change?
This is done by introducing a new common QueryBackendOptions struct which contains all configuration information necessary to select the correct backend to execute API queries against. The new TUI options embeds this struct just like all other commands, and core query logic has been updated to use QueryBackendOptions.
Does this PR rely on any other PRs?
How does this PR impact users? (This is the kind of thing that goes in release notes!)
kubectl cost tuisupports the--kubecost-namespaceand--service-nameflags.Links to Issues or ZD tickets this PR addresses or fixes
How was this PR tested?
Tested by running TUI with custom flags. Confirmed no regression by running integration.sh
Have you made an update to documentation?
N/A