Skip to content

Commit

Permalink
Update scaling-deployments.md (kedacore#368)
Browse files Browse the repository at this point in the history
Signed-off-by: firat.komurcu <[email protected]>
  • Loading branch information
MehmetFiratKomurcu authored Feb 16, 2021
1 parent 8fda5e1 commit bb581d7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/docs/2.2/concepts/scaling-deployments.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ spec:
The reference to the resource this ScaledObject is configured for. This is the resource KEDA will scale up/down and setup an HPA for, based on the triggers defined in `triggers:`.

To scale Kubernetes Deployments only `name` is needed to be specified, if one wants to scale a different resource such as StatefulSet or Custom Resource (that defines `/scale` subresource), appropriate `apiVersion` (following standard Kubernetes convetion, ie. `{api}/{version}`) and `kind` need to be specfied.
To scale Kubernetes Deployments only `name` is needed to be specified, if one wants to scale a different resource such as StatefulSet or Custom Resource (that defines `/scale` subresource), appropriate `apiVersion` (following standard Kubernetes convetion, ie. `{api}/{version}`) and `kind` need to be specified.

`envSourceContainerName` is an optional property that specifies the name of container in the target resource, from which KEDA should try to get environment properties holding secrets etc. If it is not defined, KEDA will try to get environment properties from the first Container, ie. from `.spec.template.spec.containers[0]`.

Expand Down

0 comments on commit bb581d7

Please sign in to comment.