|
flag.IntVar(&config.KubeQPS, "kubeqps", 10, "Kubernetes api requests per second.") |
|
flag.IntVar(&config.KubeBurst, "kubeburst", 20, "Kubernetes api requests burst limit.") |
There are two CLI flags defined in the operator:
flag.IntVar(&config.KubeQPS, "kubeqps", 10, "Kubernetes API requests per second.")
flag.IntVar(&config.KubeBurst, "kubeburst", 20, "Kubernetes API requests burst limit.")
These parameters are intended to be configurable via command-line arguments.
However, in the current Helm chart, there is no support for passing custom container args to the operator deployment. As a result, it is not possible to override kubeqps and kubeburst through Helm values.
The operator always runs with the default values (10 QPS and 20 burst), unless the deployment manifest is manually modified to inject CLI arguments.
This effectively means that Helm does not expose a configuration mechanism for these flags at the moment, and users cannot tune Kubernetes client rate limits through standard Helm configuration.
postgres-operator/cmd/main.go
Lines 38 to 39 in 4d40270
There are two CLI flags defined in the operator:
flag.IntVar(&config.KubeQPS, "kubeqps", 10, "Kubernetes API requests per second.")
flag.IntVar(&config.KubeBurst, "kubeburst", 20, "Kubernetes API requests burst limit.")
These parameters are intended to be configurable via command-line arguments.
However, in the current Helm chart, there is no support for passing custom container args to the operator deployment. As a result, it is not possible to override kubeqps and kubeburst through Helm values.
The operator always runs with the default values (10 QPS and 20 burst), unless the deployment manifest is manually modified to inject CLI arguments.
This effectively means that Helm does not expose a configuration mechanism for these flags at the moment, and users cannot tune Kubernetes client rate limits through standard Helm configuration.