mirror of
https://github.com/kyverno/kyverno.git
synced 2025-03-29 10:55:05 +00:00
correct typo in README for Kyverno 1.10+ (#8911)
Signed-off-by: Peter Jakubis <balonik32@gmail.com> Co-authored-by: treydock <tdockendorf@osc.edu>
This commit is contained in:
parent
871d8ed3ca
commit
bed463214e
2 changed files with 2 additions and 2 deletions
|
@ -756,7 +756,7 @@ Please consult the [values.yaml](./values.yaml) file before overriding `config.r
|
|||
|
||||
Running a highly-available Kyverno installation is crucial in a production environment.
|
||||
|
||||
In order to run Kyverno in high availability mode, you should set `replicaCount` to `3` or more.
|
||||
In order to run Kyverno in high availability mode, you should set `replicas` to `3` or more for desired components.
|
||||
You should also pay attention to anti affinity rules, spreading pods across nodes and availability zones.
|
||||
|
||||
Please see https://kyverno.io/docs/installation/#security-vs-operability for more informations.
|
||||
|
|
|
@ -390,7 +390,7 @@ Please consult the [values.yaml](./values.yaml) file before overriding `config.r
|
|||
|
||||
Running a highly-available Kyverno installation is crucial in a production environment.
|
||||
|
||||
In order to run Kyverno in high availability mode, you should set `replicaCount` to `3` or more.
|
||||
In order to run Kyverno in high availability mode, you should set `replicas` to `3` or more for desired components.
|
||||
You should also pay attention to anti affinity rules, spreading pods across nodes and availability zones.
|
||||
|
||||
Please see https://kyverno.io/docs/installation/#security-vs-operability for more informations.
|
||||
|
|
Loading…
Add table
Reference in a new issue