You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 9, 2022. It is now read-only.
Describe the bug
Hello! I'm currently using hpa operator for my resources and trying to implement appdynamics operator. When using custom metrics to hpa operator, it conflicts with other annotations defined in the deployment spec. It seems that the hpa operator tries to apply all annotations that it finds, instead of filtering specific annotations for HPA custom metrics.
Error log(deploy name removed for security reasons):
time="2021-05-24T15:22:19Z" level=error msg="Metric annotation for deployment <deploy_name> is invalid: APPD_DEPLOYMENT_INSTRUMENTATION_STATE"
time="2021-05-24T15:22:19Z" level=info msg="number of metrics: 0"
When this error happens, it only apply custom metrics in the hpa, breaking the builtin k8s metrics(cpu or memory).
Steps to reproduce the issue:
Install Appdynamics operator and hpa operator in the same namespace.
Configure custom metrics for hpa.
Expected behavior
HPA operator should apply hpa on custom metrics without trying to read a APPDYNAMICS annotation.
Additional context
HPA Operator version: 0.2.0
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Hello! I'm currently using hpa operator for my resources and trying to implement appdynamics operator. When using custom metrics to hpa operator, it conflicts with other annotations defined in the deployment spec. It seems that the hpa operator tries to apply all annotations that it finds, instead of filtering specific annotations for HPA custom metrics.
Error log(deploy name removed for security reasons):
When this error happens, it only apply custom metrics in the hpa, breaking the builtin k8s metrics(cpu or memory).
Steps to reproduce the issue:
Expected behavior
HPA operator should apply hpa on custom metrics without trying to read a APPDYNAMICS annotation.
Additional context
0.2.0
The text was updated successfully, but these errors were encountered: