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

AutoScaling: adding status type #1853

Closed
wants to merge 3 commits into from

Conversation

qiffang
Copy link
Contributor

@qiffang qiffang commented Mar 3, 2020

What problem does this PR solve?

Adding autoscaling status type, it includes these item:

  • Name // name is used to calculate autoscaling. For example: cpu.

  • CurrentValue // the current value of this metric.

  • TargetValue // the expect value of this metric.

  • CurrentReplicas // the current replica of the component.

  • DesiredReplicas // the expect replica of the component.

Code changes

  • Has Go code change

Does this PR introduce a user-facing change?:

NONE

@qiffang qiffang requested a review from Yisaer March 3, 2020 08:30
// BasicAutoScalerSpec describes the basic status for auto-scaling
type BaseAutoScalerStatus struct {
// name is the name of the given metric
Name string `json:"name,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

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

The metrics property in AutoScaler is a list. If we need to show the metrics value, we should make the metrics status as list.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Currently, We use one metric to calculate the autoscaling. So i think it is just show the metric in effect.

Copy link
Contributor

@Yisaer Yisaer left a comment

Choose a reason for hiding this comment

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

plz address the comment

@Yisaer
Copy link
Contributor

Yisaer commented Apr 14, 2020

supported in #2182

@Yisaer Yisaer closed this Apr 14, 2020
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.

2 participants