Automatic merge from submit-queue

Bump version of the fluentd-gcp image

Fix https://github.com/kubernetes/kubernetes/issues/37107

Follow-up of https://github.com/kubernetes/kubernetes/pull/37123

@piosz

Automatic merge from submit-queue

test: extend time for a condition to appear in status

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

Automatic merge from submit-queue

Remove Feature label from OutOfDisk e2e test

Fix https://github.com/kubernetes/kubernetes/issues/35722

Related to https://github.com/kubernetes/kubernetes/pull/35551 and https://github.com/kubernetes/kubernetes/pull/36225

Automatic merge from submit-queue

Add more logging around Pod deletion

After this PR we'll have at least V(2) level log near all Pod deletions.

@saad-ali - this is required by GKE to help with diagnosing possible problem.

cc @dchen1107 @wojtek-t

Automatic merge from submit-queue

Check sysfs Type instead of Device

Some distribution uses "none" device to mount "sysfs" type, so kube-proxy needs to list mount points and check "types" instead of "device".

fixes #37183 

```release-note
Change sysfs mountpoint tests from Device to Type to be able to find sysfs mountpoint on "none" device
```

Automatic merge from submit-queue

Test flake: ignore dig failure; wait until timeout

The intent of this test was to continue trying until the timeout has
been reached. The extra assertion makes the test fail early when it
should not.

https://github.com/kubernetes/kubernetes/issues/37144

fix 37114

Automatic merge from submit-queue

Update the timeout in CLOSE_WAIT e2e test

I see some test flakes due to the timeout being too strict,
updating to a larger value.

Adding tail -n 1, it looks like there may be leftover state for other
runs. We really only care about one of the CLOSE_WAIT entries.

Automatic merge from submit-queue

Register api.DeleteOptions for internal batch group

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**: Registers api.DeleteOptions for internal batch group

**Which issue this PR fixes**: fixes #36806

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
Register api.DeleteOptions for internal batch group
Register api.DeleteOptions for internal autoscaling group
```

Automatic merge from submit-queue

Document config options for gcp auth provider plugin.

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:

Adds source documentation for the gcp auth provider plugin config options. Shouldn't have to read through the code to understand what the options and their defaults are.


**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
none

Automatic merge from submit-queue

Include serial port output in GCP log-dump

This should help us debug reboot failures e.g. https://github.com/kubernetes/kubernetes/issues/33882
Also useful for OOM-kill investigation.

/cc @dchen1107

Automatic merge from submit-queue

Revert "Avoid hard-coding list of Node Conditions"

* we don't know how other API consumers are using node conditions (there was no prior expectation that the scheduler would block on custom conditions)
* not all conditions map directly to schedulability (e.g. `MemoryPressure`/`DiskPressure`)
* not all conditions use True to mean "unschedulable" (e.g. `Ready`)

This reverts commit 511b2eca to avoid breaking existing API users and to avoid constraining future uses of the node conditions API

Automatic merge from submit-queue

Test case for scalling down before scale up finished

Verifies that current pet (one which was created last by scale up action)
will enter running before scale down will take place

related: #30082

Automatic merge from submit-queue

Fix a link in api doc

Remove an extra symbol `, it breaks a link in api doc.
cc @caesarxuchao , thanks!

Automatic merge from submit-queue

Update Docker for Mac installation link

**What this PR does / why we need it**:

Fixes broken obsolete link about Docker for Mac installation.

Automatic merge from submit-queue

Read all resources for finalization and gc, not just preferred

Fixes #31481. 

Currently when starting namespace controller or garbage collector we only gather preferred version resources, which in case of multiple versions (you guessed it `batch/v2alpha1.CronJobs` again) isn't sufficient. This PR adds additional method which actually retrieves all resources from all versions and works on them.

@kubernetes/sig-api-machinery ptal

Automatic merge from submit-queue

[Federation][join-flags] Add flags for cluster context and secret names while joining clusters to federation.

Vast majority of cluster contexts are not RFC 1123 subdomains. Since
cluster and secret names for the API objects are derived from the
cluster context name, there is no way for users to join clusters
with such context names to federation, unless they modify the context
name in their kubeconfigs itself. That's a lot of inconvenience and
entirely goes against the goal and beats the purpose of the `kubefed`
tool. So we are providing these flags to allow users to override these
values.

Also, since users register their clusters with federation, it is makes
sense in terms of user experience to make the cluster name a positional
argument because that feels more natural. Also, specifying cluster name
in the join command as a mandatory positional argument make
`kubefed join` consistent with `kubefed unjoin`. This also means
`--cluster-context` is now made a flag and defaults to cluster name if
unspecified.

`--secret-name` also defaults to the cluster name if unspecified.

Fixes: Issue #35954

cc @kubernetes/sig-cluster-federation @quinton-hoole @irfanurrehman

Automatic merge from submit-queue

Revert "Use Gid when provisioning Gluster Volumes."

On further inspection the design in #35460 was not secure enough.  This PR reverts the change. 

This reverts commit 7a0d219d.

I see some test flakes due to the timeout being too strict,
updating to a larger value.

Adding tail -n 1, it looks like there may be leftover state for other
runs. We really only care about one of the CLOSE_WAIT entries.

This reverts commit 511b2eca.

The intent of this test was to continue trying until the timeout has
been reached. The extra assertion makes the test fail early when it
should not.

Automatic merge from submit-queue

Validate pet set scale up/down order

This change implements test cases to validate that:
- scale up will be done in order
- scale down in reverse order
- if any of the pets will be unhealthy, scale up/down will halt

related: https://github.com/kubernetes/kubernetes/issues/30082

Automatic merge from submit-queue

Filter out non-RestartAlways mirror pod in restart test.

Fixes #37202.

> A quick fix is to filter out non-RestartAlways pods. Because either RestartNever and RestartOnFailure pods could succeed, and we can not deal with terminated mirror pods very well now.

@yujuhong @gmarek 
/cc @kubernetes/sig-node

Automatic merge from submit-queue

Fields with omitempty tag should still be considered as optional

We've added an "+optional" tag while ago for optional fields. Before that OpenAPI spec generated assumed all fields with "omitempty" in their json tags are optional. This should be still the case (as well as +optional tag) until these two things happen:

- We update all documentation asking developers to use +optional (My bad, I should have added this after the +optional PR)
- We fix swagger 1.2 spec generator to use +optional instead of omitempty.

Fixes #37149

Automatic merge from submit-queue

Increase hollow-node qps limit

@saad-ali - test only change. I really need tests to be faster...

Automatic merge from submit-queue

Add kube-proxy logs to fluentd configs

Related to https://github.com/kubernetes/kubernetes/issues/37107

Makes fluentd collect logs from kube-proxy. It's completely backward-compatible change that does not cause problems currently, so I suggest not to bump version.

cc @piosz

Automatic merge from submit-queue

kubectl resource filter convert unstructured obj before apply filter …

Fix #37128 

@pwittrock @saad-ali ptal.

Automatic merge from submit-queue

Update start-kubemark-master to correctly work in case of master-comp…

@saad-ali - test only change.

Automatic merge from submit-queue

make groupVersionResource listing dynamic for namespace controller

@derekwaynecarr @kubernetes/sig-api-machinery 

```release-note
Third party resources are now deleted when a namespace is deleted.
```

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

Revert "Add log rotation to kubemark"

Automatic merge from submit-queue

Fix etcd unavailable error when performing kube-up.sh for Ubuntu prov…

**What this PR does / why we need it**:
This PR fixes 'etcd unavailable error' when performing kube-up.sh for Ubuntu provider

**Which issue this PR fixes** 
fixes: https://github.com/kubernetes/kubernetes/issues/36340

Some distribution, or installation use "none" device to mount sysfs (eg. Scaleway VPS). We should check the mount type instead of device.

Fix #37183

Automatic merge from submit-queue

add test file for autoscaling defaults

add test file `pkg/apis/autoscaling/v1/defaults_test.go`