We don't call klog.InitFlags yet, because that will cause a flag
redefinition error until we get everyone to stop using glog. That
will happen when we update to k8s 1.13.
This is going to be in componentconfig soon, so it would be nice to
have the same types.
These flags were recently mapped in #6361 and have not yet been in a
release - it's now or never! (Though technically it is only the
AuditWebhookBatchThrottleEnable that won't parse identically)
Also added tests!
We still need the reflect helpers, but we allow for clients to
register their own pretty-printers, which avoids the package
dependency for our pretty-printer. We register our pretty printers in
an init function in the relevant package (in this case,
upup/pkg/fi/printers.go)
Fix#5551
The current kube manifest redirect all the logs into host located log files, this PR uses the tee command to pipe into both local logs (retaining the current) and docker stdout (which will be picked up by the journald or which every logging your using. Note also permits as to now need the logs via the kubectl command.
- renamed some of the files to make things cleaner
- redirecting the logs from the kubernetes components into local file and stdout
- cleaned up any vetting or linting error i came across
- fixed any of the vettting / formatting issues that i'm came across on the update
- removed the commented out lines from the componentconfig as it make its increasingly difficult to find what is supported, what is not and the difference between them.
- added SerializeImagePulls, RegisterSchedulable to kubelet (by default they are ignored)
- added FeatureGates to the kube-proxy
Out of interest can someone point me to where these multi-versioned componentconfig are being used?
Otherwise we were not evicting based on low inodes
Also add the notion of a flag-default, so we can pass fewer spurious
flags, and gget closer to the component model
mikesplain
Anders Eknert
Rodrigo Menezes
Justin SB
Justin Santa Barbara
chrislovecnm
Rohith
Austin Moore