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

HPAContainerMetrics Version V2Beta2 Cannot Implement on Kubernetes 1.30 as "V2Beta2" was remove since Kubernetes 1.26 #124745

Open
praparn opened this issue May 8, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling.

Comments

@praparn
Copy link

praparn commented May 8, 2024

What happened?

Base on HPA/v2beta2 was removed since Kubernetes 1.26 and current HPA/V2 is not support "unknown field "spec.containerMetrics", unknown field "spec.metrics[0].resource.container". So just want suggestion for implement HPAContainerMetrics on cluster.

328572042-781024d1-7647-43a7-8481-4503f0a9c404

What did you expect to happen?

HPAContainerMetrics should working fine on Kubernetes 1.30 as GA feature gate

How can we reproduce it (as minimally and precisely as possible)?

Yes base on issue of syntact api version v2beta2 is not avaliable on Kubernetes 1.30 for create this hpa

Anything else we need to know?

No response

Kubernetes version

1.30.0

Cloud provider

AWS Cloud Controller

OS version

Ubuntu 22.04

Install tools

Container runtime (CRI) and version (if applicable)

Containerd

Related plugins (CNI, CSI, ...) and versions (if applicable)

@praparn praparn added the kind/bug Categorizes issue or PR as related to a bug. label May 8, 2024
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 8, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 8, 2024
@neolit123
Copy link
Member

/sig autoscaling

@k8s-ci-robot k8s-ci-robot added sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling.
Projects
None yet
Development

No branches or pull requests

3 participants