kubernetes/cmd/kube-apiserver/app/options
Patrick Ohly 4df70dfd41 component-base: initialize logging as soon as possible
In various places log messages where emitted as part of validation or even
before it (for example, cli.PrintFlags). Those log messages did not use the
final logging configuration, for example text output instead of JSON or not the
final verbosity. The last point became more obvious after moving the setup of
verbosity into logs.Options.Apply because PrintFlags never printed anything
anymore.

In order to force applications to deal with logging as soon as possible, the
Options.Validate and Options.Apply methods are now private. Applications should
use the new Options.ValidateAndApply directly after parsing.
2021-11-03 11:55:54 +01:00
..
globalflags_providerless.go generated: Run hack/update-gofmt.sh 2021-08-24 15:47:49 -04:00
globalflags_providers.go generated: Run hack/update-gofmt.sh 2021-08-24 15:47:49 -04:00
globalflags_test.go initialize logging after flag parsing 2021-09-30 13:46:49 +02:00
globalflags.go make it possible to start kube-api-server and kube-controller-manager without legacy cloud provider flags 2019-08-22 14:53:35 -07:00
options_test.go run hack/update-netparse-cve.sh 2021-08-20 10:42:09 +02:00
options.go Add distributed tracing to the apiserver using OpenTelemetry 2021-06-25 05:20:27 -07:00
validation_test.go move IPv6DualStack feature to stable. (#104691) 2021-09-24 16:30:22 -07:00
validation.go component-base: initialize logging as soon as possible 2021-11-03 11:55:54 +01:00