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
support portName in HTTPScaledObject service scaleTargetRef (#1174)
* support portName in HTTPScaledObject service scaleTargetRef
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
* mutually exclusive port and portName
Co-authored-by: Jirka Kremser <535866+jkremser@users.noreply.github.com>
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
* make manifests
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
* fix CEL syntax
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
* e2e test for portName
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
* use service lister instead of endpoints cache to get port from portName
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
* docs for v0.8.1 HTTPScaledObject
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
---------
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
Co-authored-by: Jirka Kremser <535866+jkremser@users.noreply.github.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ This changelog keeps track of work items that have been completed and are ready
23
23
24
24
### New
25
25
26
+
-**General**: Support portName in HTTPScaledObject service scaleTargetRef ([#1174](https://github.com/kedacore/http-add-on/issues/1174))
26
27
-**General**: Support setting multiple TLS certs for different domains on the interceptor proxy ([#1116](https://github.com/kedacore/http-add-on/issues/1116))
27
28
-**General**: TODO ([#TODO](https://github.com/kedacore/http-add-on/issues/TODO))
This annotation will disable the ScaledObject generation and management but keeping the routing and metrics available. This is done removing the current ScaledObject if it has been already created, allowing to use user managed ScaledObjects pointing the add-on scaler directly (supporting all the ScaledObject configurations and multiple triggers). You can read more about this [here](./../../walkthrough.md#integrating-http-add-on-scaler-with-other-keda-scalers)
43
+
44
+
45
+
## `hosts`
46
+
47
+
These are the hosts to apply this scaling rule to. All incoming requests with one of these values in their `Host` header will be forwarded to the `Service` and port specified in the below `scaleTargetRef`, and that same `scaleTargetRef`'s workload will be scaled accordingly.
48
+
49
+
## `pathPrefixes`
50
+
51
+
>Default: "/"
52
+
53
+
These are the paths to apply this scaling rule to. All incoming requests with one of these values as path prefix will be forwarded to the `Service` and port specified in the below `scaleTargetRef`, and that same `scaleTargetRef`'s workload will be scaled accordingly.
54
+
55
+
## `scaleTargetRef`
56
+
57
+
This is the primary and most important part of the `spec` because it describes:
58
+
59
+
1. The incoming host to apply this scaling rule to.
60
+
2. What workload to scale.
61
+
3. The service to which to route HTTP traffic.
62
+
63
+
### `deployment` (DEPRECTATED: removed as part of v0.9.0)
64
+
65
+
This is the name of the `Deployment` to scale. It must exist in the same namespace as this `HTTPScaledObject` and shouldn't be managed by any other autoscaling system. This means that there should not be any `ScaledObject` already created for this `Deployment`. The HTTP Add-on will manage a `ScaledObject` internally.
66
+
67
+
### `name`
68
+
69
+
This is the name of the workload to scale. It must exist in the same namespace as this `HTTPScaledObject` and shouldn't be managed by any other autoscaling system. This means that there should not be any `ScaledObject` already created for this workload. The HTTP Add-on will manage a `ScaledObject` internally.
70
+
71
+
### `kind`
72
+
73
+
This is the kind of the workload to scale.
74
+
75
+
### `apiVersion`
76
+
77
+
This is the apiVersion of the workload to scale.
78
+
79
+
### `service`
80
+
81
+
This is the name of the service to route traffic to. The add-on will create autoscaling and routing components that route to this `Service`. It must exist in the same namespace as this `HTTPScaledObject` and should route to the same `Deployment` as you entered in the `deployment` field.
82
+
83
+
### `port`
84
+
85
+
This is the port to route to on the service that you specified in the `service` field. It should be exposed on the service and should route to a valid `containerPort` on the `Deployment` you gave in the `deployment` field.
86
+
87
+
### `portName`
88
+
89
+
Alternatively, the port can be referenced using it's `name` as defined in the `Service`.
90
+
91
+
### `targetPendingRequests` (DEPRECTATED: removed as part of v0.9.0)
92
+
93
+
>Default: 100
94
+
95
+
This is the number of _pending_ (or in-progress) requests that your application needs to have before the HTTP Add-on will scale it. Conversely, if your application has below this number of pending requests, the HTTP add-on will scale it down.
96
+
97
+
For example, if you set this field to 100, the HTTP Add-on will scale your app up if it sees that there are 200 in-progress requests. On the other hand, it will scale down if it sees that there are only 20 in-progress requests. Note that it will _never_ scale your app to zero replicas unless there are _no_ requests in-progress. Even if you set this value to a very high number and only have a single in-progress request, your app will still have one replica.
98
+
99
+
### `scaledownPeriod`
100
+
101
+
>Default: 300
102
+
103
+
The period to wait after the last reported active before scaling the resource back to 0.
104
+
105
+
> Note: This time is measured on KEDA side based on in-flight requests, so workloads with few and random traffic could have unexpected scale to 0 cases. In those case we recommend to extend this period to ensure it doesn't happen.
106
+
107
+
108
+
## `scalingMetric`
109
+
110
+
This is the second most important part of the `spec` because it describes how the workload has to scale. This section contains 2 nested sections (`requestRate` and `concurrency`) which are mutually exclusive between themselves.
111
+
112
+
### `requestRate`
113
+
114
+
This section enables scaling based on the request rate.
115
+
116
+
> **NOTE**: Requests information is stored in memory, aggragating long periods (longer than 5 minutes) or too fine granularity (less than 1 second) could produce perfomance issues or memory usage increase.
117
+
118
+
> **NOTE 2**: Although updating `window` and/or `granularity` is something doable, the process just replaces all the stored request count infomation. This can produce unexpected scaling behaviours until the window is populated again.
119
+
120
+
#### `targetValue`
121
+
122
+
>Default: 100
123
+
124
+
This is the target value for the scaling configuration.
125
+
126
+
#### `window`
127
+
128
+
>Default: "1m"
129
+
130
+
This value defines the aggregation window for the request rate calculation.
131
+
132
+
#### `granularity`
133
+
134
+
>Default: "1s"
135
+
136
+
This value defines the granualarity of the aggregated requests for the request rate calculation.
137
+
138
+
### `concurrency`
139
+
140
+
This section enables scaling based on the request concurrency.
141
+
142
+
> **NOTE**: This is the only scaling behaviour before v0.8.0
143
+
144
+
#### `targetValue`
145
+
146
+
>Default: 100
147
+
148
+
This is the target value for the scaling configuration.
0 commit comments