You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users may wish to run kubectl cost against an already-exposed endpoint (if Kubecost endpoints are exposed publicly) or a local version of OpenCost during development.
We could add support for this with a third query mode, kubectl cost --no-cluster --path "kubecost.example.com" (or similar) that just uses an API endpoint path to make queries and doesn't port-forward or proxy using a K8s client. Flag names TBD.
This is currently low priority. If you are interested in this functionality, please comment on this issue!
The text was updated successfully, but these errors were encountered:
Some users may wish to run
kubectl cost
against an already-exposed endpoint (if Kubecost endpoints are exposed publicly) or a local version of OpenCost during development.We could add support for this with a third query mode,
kubectl cost --no-cluster --path "kubecost.example.com"
(or similar) that just uses an API endpoint path to make queries and doesn't port-forward or proxy using a K8s client. Flag names TBD.This is currently low priority. If you are interested in this functionality, please comment on this issue!
The text was updated successfully, but these errors were encountered: