-
Notifications
You must be signed in to change notification settings - Fork 459
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
Set replicas to MaxReplicas if HPA is enabled #833
Set replicas to MaxReplicas if HPA is enabled #833
Conversation
If number of replicas in current deployment status is bigger than MaxReplicas and HPA is enabled set deployment replicas to MaxReplicas.
@binjip978 was the current behavior causing any issues? |
Yeah, during initial deployment or upgrade I saw that replicas count in status was much higher than it was specified in deployment or HPA configuration, the reason is not clear to me (maybe some issue with metrics server in our cluster) This problem is not always reproducible in our environment, but it may happen, most of time it works as expected. |
@jpkrohling could you review it as well? You did a bunch of work around HPA in Jaeger operator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is lacking tests. If e2e tests aren't easy to simulate the reported behavior, then at least unit tests should be added>
Signed-off-by: binjip978 <pdp.eleven11@gmail.com>
dbc0877
to
d9ca106
Compare
* Set replicas to MaxReplicas if HPA is enabled If number of replicas in current deployment status is bigger than MaxReplicas and HPA is enabled set deployment replicas to MaxReplicas. * Move replicas calculation in seperate function Signed-off-by: binjip978 <pdp.eleven11@gmail.com>
If number of replicas in current deployment status is bigger than
MaxReplicas and HPA is enabled set deployment replicas to MaxReplicas.