diff --git a/charts/kyverno/README.md b/charts/kyverno/README.md index 3d5ba05926..f8f56d9993 100644 --- a/charts/kyverno/README.md +++ b/charts/kyverno/README.md @@ -359,7 +359,7 @@ The command removes all the Kubernetes components associated with the chart and | reportsController.priorityClassName | string | `""` | Optional priority class | | reportsController.hostNetwork | bool | `false` | Change `hostNetwork` to `true` when you want the pod to share its host's network namespace. Useful for situations like when you end up dealing with a custom CNI over Amazon EKS. Update the `dnsPolicy` accordingly as well to suit the host network mode. | | reportsController.dnsPolicy | string | `"ClusterFirst"` | `dnsPolicy` determines the manner in which DNS resolution happens in the cluster. In case of `hostNetwork: true`, usually, the `dnsPolicy` is suitable to be `ClusterFirstWithHostNet`. For further reference: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy. | -| reportsController.extraArgs | object | `{"clientRateLimitBurst":100,"clientRateLimitQPS":300}` | Extra arguments passed to the container on the command line | +| reportsController.extraArgs | object | `{"clientRateLimitBurst":300,"clientRateLimitQPS":300}` | Extra arguments passed to the container on the command line | | reportsController.resources.limits | object | `{"memory":"128Mi"}` | Pod resource limits | | reportsController.resources.requests | object | `{"cpu":"100m","memory":"64Mi"}` | Pod resource requests | | reportsController.nodeSelector | object | `{}` | Node labels for pod assignment | diff --git a/charts/kyverno/values.yaml b/charts/kyverno/values.yaml index b8ff7baa15..d323fc1662 100644 --- a/charts/kyverno/values.yaml +++ b/charts/kyverno/values.yaml @@ -827,7 +827,7 @@ reportsController: # -- Extra arguments passed to the container on the command line extraArgs: clientRateLimitQPS: 300 - clientRateLimitBurst: 100 + clientRateLimitBurst: 300 resources: # -- Pod resource limits