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

Keda Metrics Server APIService is still v1beta1 but deployment is v1 #673

Open
jfouche-vendavo opened this issue Aug 2, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jfouche-vendavo
Copy link

A clear and concise description of what the bug is.
The APIService for metrics server is marked v1beta1 wherease the metrics server deployment is v1. Which one is correct?

Expected Behavior

Mark both services as v1beta1 OR v1.

Actual Behavior

APIService is marked v1beta1
Metrics Server deployment is marked v1

Steps to Reproduce the Problem

$>k get apiservice v1beta1.external.metrics.k8s.io -oyaml | grep v1beta1
app.kubernetes.io/name: v1beta1.external.metrics.k8s.io
name: v1beta1.external.metrics.k8s.io
version: v1beta1

$>kubectl get deploy keda-operator-metrics-apiserver -oyaml | grep v1
apiVersion: apps/v1
apiVersion: v1

Or view the source here: APIService:

app.kubernetes.io/name: v1beta1.external.metrics.k8s.io

Specifications

  • KEDA Version: ghcr.io/kedacore/keda-metrics-apiserver:2.14.0
  • Platform & Version: Linux
  • Kubernetes Version: 1.28.9
  • Scaler(s): Not sure what is required here?
@jfouche-vendavo jfouche-vendavo added the bug Something isn't working label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant