https://github.com/coredns/coredns/blob/master/plugin/cache/cache.go#L236
This gets rounded down to the nearest multiple of 256: 9984

Similar to `--no-negcache` on dnsmasq, this prevents issues which poll DNS for orchestration such as operators with StatefulSets. It can also be very confusing for users when negative caching results in a change they just made seeming to be broken until the cache expires. This assumes that 5 seconds is reasonable and will still catch repeated AAAA negative responses. We could also set the denial cache size to zero which should effectively fully disable it like dnsmasq in kube-dns but testing shows this approach seems to work well in our (albeit small) test clusters.

apis:core:validation: remove unused, changes to idiomatic go

openapi-aggregation: speed up merging from 1 sec to 50-100 ms

cleanup .import-restrictions for cloud provider

kubeadm: Refactor InitConfiguration init APIs

generated_files: remove line about /docs/.generated_docs (fix PR size plugin)

  Fix fmt.Sprintf error message

Currently ConfigFileAndDefaultsToInternalConfig and
FetchConfigFromFileOrCluster are used to default and load InitConfiguration
from file or cluster. These two APIs do a couple of completely separate things
depending on how they were invoked. In the case of

ConfigFileAndDefaultsToInternalConfig, an InitConfiguration could be either
defaulted with external override parameters, or loaded from file.
With FetchConfigFromFileOrCluster an InitConfiguration is either loaded from
file or from the config map in the cluster.

The two share both some functionality, but not enough code. They are also quite
difficult to use and sometimes even error prone.

To solve the issues, the following steps were taken:

- Introduce DefaultedInitConfiguration which returns defaulted version agnostic
  InitConfiguration. The function takes InitConfiguration for overriding the
  defaults.

- Introduce LoadInitConfigurationFromFile, which loads, converts, validates and
  defaults an InitConfiguration from file.

- Introduce FetchInitConfigurationFromCluster that fetches InitConfiguration
  from the config map.

- Reduce, when possible, the usage of ConfigFileAndDefaultsToInternalConfig by
  replacing it with DefaultedInitConfiguration or LoadInitConfigurationFromFile
  invocations.

- Replace all usages of FetchConfigFromFileOrCluster with calls to
  LoadInitConfigurationFromFile or FetchInitConfigurationFromCluster.

- Delete FetchConfigFromFileOrCluster as it's no longer used.

- Rename ConfigFileAndDefaultsToInternalConfig to
  LoadOrDefaultInitConfiguration in order to better describe what the function
  is actually doing.
Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>

Fixed import-boss godoc comment formatting

Fix function comment to consistent with its name

Fix function comment to consistent with its name

Signed-off-by: zhoulin xie <zhoulin.xie@daocloud.io>

update from base repository

Add a case to illustrate how to use `kubectl get -o custom-columns`

Change-Id: I8f9b8a28474d12d6eb74ecef85a988dd3f1f851e

Fixes inconsistent behaviour in portforward

Signed-off-by: PingWang <wang.ping5@zte.com.cn>

Merge pull request #69086 from bruceauyeung/log-useful-info-instead-of-silent-exit-when-etcd-already-installed

log useful information instead of silent exit without error

Improve in-cluster-client-conf client-go docs

Make CRD column printers consistent with typed printers

Make a small formatting change to make it clear that you must take the
RBAC actions regardless of whether you're using Minikube or not.

Almost all other server side printers use duration.HumanDuration
which has higher precision output. Switch CRD printers to use this
as well.

The rules for address parsing are:

* Explicitly specified addresses must bind successfully
* `localhost` is pinned to `127.0.0.1` and `::1` and at least one of those must bind successfully

This change also makes output of the command consistent
between runs with the same arguments.
Previously the command was using the range via map of addresses
which sometimes was producing different output because the order
of values is not guaranteed in Go.

Add metric exposing amount of processed init events in watchcache

kubeadm: add a preflight check for Docker and cgroup driver

Fix linting in cmd/kubemark package

Kubelet: add usageNanoCores from CRI stats provider

fix shellcheck in node-api