/usr/bin/pod_nanny

I1108 02:45:29.295882       2 pod_nanny.go:86] Invoked by [/usr/bin/pod_nanny --help]
I1108 02:45:29.295960       2 pod_nanny.go:87] Version: addon-resizer
Usage of /usr/bin/pod_nanny:
      --address string                            The address to expose Prometheus metrics. (default ":8945")
      --config-dir string                         Path of configuration containing base resource requirements. (default "MISSING")
      --container string                          The name of the container to watch. This defaults to the nanny itself. (default "pod-nanny")
      --cpu string                                The base CPU resource requirement.
      --deployment string                         The name of the deployment being monitored. This is required.
      --estimator string                          The estimator to use. Currently supported: linear, exponential (default "linear")
      --expose-metrics                            When true, exposes Prometheus metrics on the port specified by the address flag.
      --extra-cpu string                          The amount of CPU to add per resource.
      --extra-memory string                       The amount of memory to add per resource.
      --extra-storage string                      The amount of storage to add per resource. (default "0Gi")
      --healthcheck-address string                The address to expose an HTTP health-check on. (default ":8080")
      --kubeconfig string                         absolute path to the kubeconfig file specifying the apiserver instance.
      --leader-election-enable                    Whether leader election should be used.
      --leader-election-lease-duration duration   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. (default 15s)
      --leader-election-renew-deadline duration   The duration that the acting master will retry refreshing leadership before giving up. (default 10s)
      --leader-election-retry-period duration     The duration to wait between tries of actions. (default 2s)
      --memory string                             The base memory resource requirement.
      --minClusterSize uint                       The smallest number of resources will be scaled to. Must be > 1. This flag is used only when an exponential estimator is used. (default 16)
      --namespace string                          The namespace of the ward. This defaults to the nanny pod's own namespace.
      --nanny-config-map-name string              The name of the ConfigMap of NannyConfiguration. Specify when getting nanny config updates through API calls.
      --pod string                                The name of the pod to watch. This defaults to the nanny's own pod. When running in a different pod, this will be empty and information will be obtained from deployment instead.
      --poll-period int                           The time, in milliseconds, to poll the dependent container. (default 10000)
      --run-on-control-plane                      Whether the addon-resizer is running on the control plane.
      --scale-down-delay duration                 The time to wait after the addon-resizer start or last scaling operation before the scale down can be performed.
      --scale-up-delay duration                   The time to wait after the addon-resizer start or last scaling operation before the scale up can be performed.
      --scaling-mode string                       The mode of scaling to be used. Possible values: 'node-proportional' or 'container-proportional' (default "node-proportional")
      --storage string                            The base storage resource requirement. (default "MISSING")
      --threshold int                             A number between 0-100. The dependent's resources are rewritten when they deviate from expected by more than threshold.
      --use-metrics                               Whether to use apiserver metrics to detect cluster size instead of the default method of listing objects from the Kubernetes API.
pflag: help requested