Automatic merge from submit-queue

Check fluentd deployment befure running cluster logging e2e tests

There were changes to the way cluster logging is deployed to the cluster.

PR adds logic to the cluster logging e2e tests to check that cluster has fluentd and that there's only one fluentd instance on the node. This will verify the correctness of the deployment method.

Automatic merge from submit-queue

Add readme for fluentd addons

/cc @steveperry-53

Automatic merge from submit-queue

Fix adding disks to more than one scsi adapter. Fixes #42399

**What this PR does / why we need it**: Allows a single node to use more than 16 disks.

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #42399

**Special notes for your reviewer**: 

**Release note**:

```release-note
Fix adding disks to more than one scsi adapter.
```

Automatic merge from submit-queue

Add an env KUBE_ENABLE_MASTER_NOSCHEDULE_TAINT and disable it by default

This PR changed master `NoSchedule` taint to opt-in.

As is discussed with @bgrant0607 @janetkuo, `NoSchedule` master taint breaks existing user workload, we should not enable it by default.

Previously, NPD required the taint because it can only support one OS distro with a specific configuration. If master and node are using different OS distros, NPD will not work either on master or node. However, we've already fixed this in https://github.com/kubernetes/kubernetes/pull/40206, so for NPD it's fine to disable the taint.

This should work, but I'll still try it in my cluster to confirm.

@kubernetes/sig-scheduling-misc @dchen1107 @mikedanese

Automatic merge from submit-queue (batch tested with PRs 43533, 43539)

kuberuntime: don't override the pod IP for pods using host network

This fixes the issue of not passing pod IP via downward API for host network pods.

Automatic merge from submit-queue

Fix the ETCD env vars for downgrade

Automatic merge from submit-queue

bump Kubernetes packaged CNI to v0.5.1

Update version of packaged CNI to v0.5.1 in order as part of a fix for #43488.

Next steps compiling these versions and updating references to artifacts.

/cc @ixdy

Automatic merge from submit-queue (batch tested with PRs 43465, 43529, 43474, 43521)

Added retransmissions in service call by e2e resource consumer library.

Added retransmissions in service call by e2e resource consumer library.
Fixes #43187.

```release-note
NONE
```

Automatic merge from submit-queue (batch tested with PRs 43465, 43529, 43474, 43521)

kubelet/cni: hook network plugin Status() up to CNI network discovery

Ensure that the plugin returns NotReady status until there is a
CNI network available which can be used to set up pods.

Fixes: https://github.com/kubernetes/kubernetes/issues/43014

I think the only reason it wasn't done like this in the first place was that the dynamic "reread /etc/cni/net.d every 10s forever" was added long after the Status() hook was.  What do you think?

@freehan @caseydavenport @luxas @jbeda

Automatic merge from submit-queue (batch tested with PRs 43465, 43529, 43474, 43521)

link the server.key to the key not the crt

Automatic merge from submit-queue

Disable readyReplicas validation for Deployments

Because there is no field in 1.5, when we update to 1.6 and the
controller tries to update the Deployment, it will be denied by
validation because the pre-existing availableReplicas field is greater
than readyReplicas (normally readyReplicas should always be greater or
equal).

Fixes https://github.com/kubernetes/kubernetes/issues/43392

@kubernetes/sig-apps-bugs

Automatic merge from submit-queue (batch tested with PRs 43513, 43499)

Make kubectl replace unconditional

second attempt at https://github.com/kubernetes/kubernetes/pull/43192

rather than a retry, make the replace unconditional, which works reliably

Automatic merge from submit-queue (batch tested with PRs 43513, 43499)

Fix Cluster-Autoscaler e2e failing on some node configs

This fixes a cluster-autoscaler e2e failure on some node configs (namely if memory capacity == allocatable memory).

**Release note**:
```release-note
```

Added retransmissions in service call by e2e resource consumer library.
Fixes #43187.

Because there is no field in 1.5, when we update to 1.6 and the
controller tries to update the Deployment, it will be denied by
validation because the pre-existing availableReplicas field is greater
than readyReplicas (normally readyReplicas should always be greater or
equal).

Automatic merge from submit-queue

Add validation for affinities and taints/tolerations annotations.

It fixes annotations validation issues for pod/node affinities and taints/tolerations annotations for 1.5 to 1.6 upgrade tests as discussed in the issue https://github.com/kubernetes/kubernetes/issues/43228 .

@davidopp @derekwaynecarr @kubernetes/sig-scheduling-pr-reviews

Automatic merge from submit-queue

update influxdb dependency to v1.1.1 and change client to v2

**What this PR does / why we need it**:
1. it updates version of influxdb libraries used by tests to v1.1.1 to match version used by grafana
2. it switches influxdb client to v2 to address the fact that [v1 is being depricated](https://github.com/influxdata/influxdb/tree/v1.1.1/client#description)

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:
cc @piosz 
1. [vendor/BUILD](https://github.com/KarolKraskiewicz/kubernetes/blob/master/vendor/BUILD)  didn't get regenerated after executing `./hack/godep-save.sh` so I left previous version.
Not sure how to trigger regeneration of this file.
2. `tests/e2e/monitoring.go` seem to be passing without changes, even after changing version of the client. 

**Release note**:

```release-note
```

Automatic merge from submit-queue (batch tested with PRs 43492, 43489)

Authorize PSP usage for pods without service accounts

Fixes #43459

```release-note
PodSecurityPolicy authorization is correctly enforced by the PodSecurityPolicy admission plugin.
```

Automatic merge from submit-queue

Update Changelog for 1.5.5

Update changelog for 1.5.5 to capture change details now that [vulnerability has been disclosed](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/kubernetes-announce/7tvmimkHj0k/RLlImP_kBwAJ).

Automatic merge from submit-queue (batch tested with PRs 43481, 43419, 42741, 43480)

[Federation] Increase the federation components logging verbosity level in e2e tests.

**Release note**:

```release-note
NONE
```

cc @kubernetes/sig-federation-pr-reviews 

/assign @csbell

Automatic merge from submit-queue (batch tested with PRs 43481, 43419, 42741, 43480)

controller: work around milliseconds skew in AddAfter

AddAfter is not requeueing precisely after the provided time and may
skew for some millieseconds. This is really important because controllers
don't relist often so a missed check because of ms difference is
essentially dropping the key. For example, in [1] the test requeues a
Deployment for a progress check after 10s[2] but the Deployment is synced
9ms earlier ending up in the controller not recognizing the Deployment as
failed thus dropping it from the queue w/o any error. The drop is fixed by
forcing the controller to resync the Deployment but we are going to resync
after the full duration.

@deads2k if you don't like this I am going to handle this on a case by case basis

[1] https://github.com/kubernetes/kubernetes/issues/39785#issuecomment-279959133
[2] https://github.com/kubernetes/kubernetes/blob/c48b2cab0f25abd374ae9308afb19735a4150e19/test/e2e/deployment.go#L1122

Automatic merge from submit-queue (batch tested with PRs 43481, 43419, 42741, 43480)

Add e2e test for DaemonSet node selector updates

@kargakis @lukaszo @kubernetes/sig-apps-bugs

Automatic merge from submit-queue (batch tested with PRs 43481, 43419, 42741, 43480)

Add ETCD env vars for downgrade

This is a partial fix for https://github.com/kubernetes/kubernetes/issues/43470

Automatic merge from submit-queue

Renamed fluentd-ds-ready annotation

We don't want to have alpha annotation as production ready solution.

Low risk change, only rename.