I noticed that global.logLevel is not documented in the Helm README file:
|
| `global.imagePullSecrets` | Reference to one or more secrets to be used when pulling images | `[]` | |
|
| `global.commonLabels` | Labels to apply to all resources | `{}` | |
|
| `global.rbac.create` | If `true`, create and use RBAC resources (includes sub-charts) | `true` | |
|
| `global.priorityClassName`| Priority class name for cert-manager and webhook pods | `""` | |
|
| `global.podSecurityPolicy.enabled` | If `true`, create and use PodSecurityPolicy (includes sub-charts) | `false` | |
|
| `global.podSecurityPolicy.useAppArmor` | If `true`, use Apparmor seccomp profile in PSP | `true` | |
|
| `global.leaderElection.namespace` | Override the namespace used to store the ConfigMap for leader election | `kube-system` | |
|
| `global.leaderElection.leaseDuration` | The duration that non-leader candidates will wait after observing a leadership renewal until attempting to acquire leadership of a led but unrenewed leader slot. This is effectively the maximum duration that a leader can be stopped before it is replaced by another candidate | | |
|
| `global.leaderElection.renewDeadline` | The interval between attempts by the acting master to renew a leadership slot before it stops leading. This must be less than or equal to the lease duration | | |
|
| `global.leaderElection.retryPeriod` | The duration the clients should wait between attempting acquisition and renewal of a leadership | | |
/kind bug
Originally posted by @wallrj in #5860 (review)