codespell corrections in data and layouts (#482)
Signed-off-by: Robin Tweedie <robin@wayve.ai>
This commit is contained in:
parent
fba922ad85
commit
8d4cde7237
|
@ -69,7 +69,7 @@ client](https://godoc.org/k8s.io/client-go/dynamic) from the `client-go` package
|
|||
[GroupVersionResource](https://godoc.org/k8s.io/apimachinery/pkg/runtime/schema#GroupVersionResource)
|
||||
describing the type of resource to be accessed and returns a
|
||||
[NamespaceableResourceInterface](https://godoc.org/k8s.io/client-go/dynamic#NamespaceableResourceInterface)
|
||||
which contains methods to retrieve, create, or maniuplate that resource. Here's a code sample
|
||||
which contains methods to retrieve, create, or manipulate that resource. Here's a code sample
|
||||
containing a function that retrieves a KEDA `ScaledObject` resource by name.
|
||||
|
||||
```go
|
||||
|
|
|
@ -42,7 +42,7 @@ KEDA allows you to use multiple triggers as part of the same `ScaledObject` or `
|
|||
|
||||
By doing this, your autoscaling becomes better:
|
||||
- All your autoscaling rules are in one place
|
||||
- You will not have multiple `ScaledObject`'s or `ScaledJob`'s interferring with each other
|
||||
- You will not have multiple `ScaledObject`'s or `ScaledJob`'s interfering with each other
|
||||
|
||||
KEDA will start scaling as soon as when one of the triggers meets the criteria. Horizontal Pod Autoscaler (HPA) will calculate metrics for every scaler and use the highest desired replica count to scale the workload to.
|
||||
"""
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
Woops! Dead link...
|
||||
</p>
|
||||
|
||||
That's not very conventient, sorry about that!
|
||||
That's not very convenient, sorry about that!
|
||||
|
||||
Maybe you were looking for:
|
||||
<ul>
|
||||
|
|
Loading…
Reference in New Issue