[enterprise-4.19] Custom Metrics Autoscaler compilation PR #99358
Conversation
openshift-ci
bot
added
the
size/L
|
🤖 Thu Sep 18 20:20:24 - Prow CI generated the docs preview: |
| * If you are using a secret, the `Secret` object must exist, for example: | ||
| * If you are using a bound service account token, the service account must exist. | ||
| * If you are using a bound service account token, a role-based access control (RBAC) object that enables the Custom Metrics Autoscaler Operator to request service account tokens from the service account must exist. |
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use '(?<!.*-)operator' instead of 'Operator'.
|
|
||
| You can scale pods based on the number of pods matching a specific label selector. | ||
|
|
||
| The Custom Metrics Autoscaler Operator tracks the number of pods with a specific label that are in the same namespace, then calculates a _relation_ based on the number of labeled pods to the pods for the scaled object. Using this relation, the Custom Metrics Autoscaler Operator scales the object according to the scaling policy in the `ScaledObject` or `ScaledJob` specification. |
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use '(?<!.*-)operator' instead of 'Operator'.
|
|
||
| You can scale pods based on the number of pods matching a specific label selector. | ||
|
|
||
| The Custom Metrics Autoscaler Operator tracks the number of pods with a specific label that are in the same namespace, then calculates a _relation_ based on the number of labeled pods to the pods for the scaled object. Using this relation, the Custom Metrics Autoscaler Operator scales the object according to the scaling policy in the `ScaledObject` or `ScaledJob` specification. |
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use '(?<!.*-)operator' instead of 'Operator'.
|
|
||
| The pod counts includes pods with a `Succeeded` or `Failed` phase. | ||
|
|
||
| For example, if you have a `frontend` deployment and a `backend` deployment. You can use a `kubernetes-workload` trigger to scale the `backend` deployment based on the number of `frontend` pods. If number of `frontend` pods goes up, the Operator would scale the `backend` pods to maintain the specified ratio. In this example, if there are 10 pods with the `app=frontend` pod selector, the Operator scales the backend pods to 5 in order to maintain the `0.5` ratio set in the scaled object. |
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use '(?<!.*-)operator' instead of 'Operator'.
|
|
||
| The pod counts includes pods with a `Succeeded` or `Failed` phase. | ||
|
|
||
| For example, if you have a `frontend` deployment and a `backend` deployment. You can use a `kubernetes-workload` trigger to scale the `backend` deployment based on the number of `frontend` pods. If number of `frontend` pods goes up, the Operator would scale the `backend` pods to maintain the specified ratio. In this example, if there are 10 pods with the `app=frontend` pod selector, the Operator scales the backend pods to 5 in order to maintain the `0.5` ratio set in the scaled object. |
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use '(?<!.*-)operator' instead of 'Operator'.
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Manual cherrypick of #99294