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

Add KEDAScalersInfo to display important information #6330

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

Conversation

rickbrouwer
Copy link
Contributor

Adding a new event (KEDAScalersInfo) so that important information is shown in e.g. Argo CD.
Added the deprecation info message by the cpu_memory_scaler and ibmmq_scaler.

Checklist

Fixes #6328

@rickbrouwer rickbrouwer requested a review from a team as a code owner November 12, 2024 16:32
@rickbrouwer rickbrouwer marked this pull request as draft November 12, 2024 16:32
@rickbrouwer rickbrouwer force-pushed the scalerinfo branch 5 times, most recently from ee11028 to 0fef06b Compare November 12, 2024 17:12
@rickbrouwer rickbrouwer marked this pull request as ready for review November 12, 2024 17:29
Copy link
Member

@wozniakjan wozniakjan left a comment

Choose a reason for hiding this comment

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

would it be possible to include these events in the TypedConfig deprecated logic?

I can imagine we may want to add something like "DeprecatedEvent" parameter to model this behaviour, because iirc the "Deprecated" parameter present there will error the scaler parsing. Or maybe we change the current behaviour to not fail and throw event instead?

@@ -58,7 +66,6 @@ func parseResourceMetadata(config *scalersconfig.ScalerConfig, logger logr.Logge

// This is deprecated and can be removed later
if meta.Type != "" {
logger.Info("The 'type' setting is DEPRECATED and will be removed in v2.18 - Use 'metricType' instead.")
Copy link
Member

Choose a reason for hiding this comment

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

nit: does it make sense to keep both events as well as log messages regarding deprecated fields?

Copy link
Member

Choose a reason for hiding this comment

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

I think it make sense to keep both

@rickbrouwer rickbrouwer marked this pull request as draft November 14, 2024 15:35
@rickbrouwer rickbrouwer force-pushed the scalerinfo branch 5 times, most recently from 9a79002 to 81e6f6c Compare November 14, 2024 17:43
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.

New eventreason KEDAScalersInfo to display important information
3 participants