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

[feat]: Integrate Kubernetes Metrics API into the Python Client #2135

Open
Parvezkhan0 opened this issue Oct 20, 2023 · 3 comments
Open

[feat]: Integrate Kubernetes Metrics API into the Python Client #2135

Parvezkhan0 opened this issue Oct 20, 2023 · 3 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Parvezkhan0
Copy link

What is the feature and why do you need it:

The feature is the integration of the Kubernetes Metrics API into the Python client. This addition will allow users to retrieve metrics data directly through the client, enabling more streamlined monitoring and auto-scaling workflows. Currently, the client lacks native support for querying metrics data, making it necessary to rely on external tools or libraries.

Describe the solution you'd like to see:

I envision the addition of a new module or extension to the existing client specifically dedicated to handling metrics data retrieval. This module should include methods for querying various types of metrics, such as pod metrics, node metrics, and custom metrics. It should also be designed to seamlessly integrate with the existing client structure, providing a consistent user experience.

The solution should ensure compatibility with different versions of Kubernetes to support users on various clusters. Additionally, comprehensive documentation and examples should be provided to guide users in effectively utilizing the new metrics functionalities.

Overall, the goal is to empower users with the ability to access and utilize metrics data directly through the Python client, eliminating the need for external dependencies and enhancing the client's capabilities in monitoring and scaling applications.

@Parvezkhan0 Parvezkhan0 added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 20, 2023
@roycaihw
Copy link
Member

/help

@Parvezkhan0 Could you elaborate what Kubernetes Metrics API is?

@k8s-ci-robot
Copy link
Contributor

@roycaihw:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

@Parvezkhan0 Could you elaborate what Kubernetes Metrics API is?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Oct 23, 2023
@rodrigodelmonte
Copy link

I believe the metrics=server is the component responsible for exposing metrics for the HPA controller or the kubectl top command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants