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

Deprecation cleanup for 2.12 release #4899

Closed
dttung2905 opened this issue Aug 23, 2023 · 5 comments · Fixed by #4806
Closed

Deprecation cleanup for 2.12 release #4899

dttung2905 opened this issue Aug 23, 2023 · 5 comments · Fixed by #4806

Comments

@dttung2905
Copy link
Contributor

Hi team,
I create this issue to track the deprecation clean up for 2.12 release. Included in this clean up are the following issues: ( may be more than one )

@lefterisALEX
Copy link

lefterisALEX commented Oct 13, 2023

Is that removed from all scalers? Was testing 2.12.0 version with the following scaled object and still works.

apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: "sample-scaled-object"
spec:
  pollingInterval: 30
  minReplicaCount: 2
  maxReplicaCount: 10
 
  scaleTargetRef:
    name: "swiss-knife"
 
  triggers:
    - type: prometheus
      metadata:
        serverAddress: http://kube-prometheus-stack-thanos-query-frontend.kube-system:9090/
        metricName: nginx_ingress_controller_requests
        query: |
          sum(
              rate(
                  nginx_ingress_controller_requests{
                      exported_namespace="kube-system",
                      exported_service="hubble-ui",
                  }[2m]
              )
          )

        threshold: "1"
       ```

@zroubalik
Copy link
Member

The ScaledObject will work, but the property is not used anymore.

@lefterisALEX
Copy link

thanks for the quick response, that means the line with the metricName do not any difference if we have it or not?

@zroubalik
Copy link
Member

Yes, if you want to assigne name to this trigger, use trigger.name.

@lefterisALEX
Copy link

maybe i am not aware about it , but how this can be a breaking change? Might be that the value of the metricName be used for something else and by removing it this will break?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants