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

Jsonnet: Remove depracated KEDA parameters #10737

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

zhuoyuan-liu
Copy link

What this PR does

This parameter is deprecated in KEDA 2.10 and now KEDA is 2.15. All the relevant metrics have been updated in the previous PR and this parameter has not been used anymore.

Which issue(s) this PR fixes or relates to

Fixes #

Checklist

  • Tests updated.
  • Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • about-versioning.md updated with experimental features.

@zhuoyuan-liu zhuoyuan-liu requested a review from a team as a code owner February 25, 2025 12:05
@CLAassistant
Copy link

CLAassistant commented Feb 25, 2025

CLA assistant check
All committers have signed the CLA.

// The metric name uniquely identifies a metric in the KEDA metrics server.
// This is deprecatd in KEDA 2.10, and is instead set to a default based on the trigger type (e.g. `s0-prometheus`).
// Instead we use the metric_name as the name for the trigger (above). This appears as the `scaler` label on `keda_scaler_metrics_value`.
metricName: trigger.metric_name,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we switch to name instead of metricName now? https://keda.sh/docs/2.16/reference/scaledobject-spec/#triggers

@dimitarvdimitrov
Copy link
Contributor

Thanks for the contribution!

All the relevant metrics have been updated in the previous PR and this parameter has not been used anymore.

can you link that previous PR?

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

Successfully merging this pull request may close these issues.

3 participants