Skip to content
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.

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

Add support for providing just an endpoint to hit for data, instead of proxying/port-forwarding into a cluster #120

Closed
michaelmdresser opened this issue Jun 21, 2022 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@michaelmdresser
Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants