Automatic merge from submit-queue
fix the link of doc
**What this PR does / why we need it**:
the link of doc point one pr,I think point the kubernetes documents better,thanks!
**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**:
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue
Fix several typos in CHANGELOG.md file
**What this PR does / why we need it**:
Fixed several typos in CHANGELOG.md file.
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
NONE
**Special notes for your reviewer**:
NONE
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue
Add kube-proxy change notice to v1.7.3 release note
**What this PR does / why we need it**: Add necessary release note for issue #48600.
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes#48600
**Special notes for your reviewer**:
This is suppose to be in v1.7.3 release note, but turned out I only updated release note on the cherrypick PR (#49799) instead of the original PR (#48625) so nothing got picked up :(
/assign @bowei @wojtek-t
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue
Delete reduandant *
**What this PR does / why we need it**:
Delete reduandant *
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue
fix style of yaml and text
**What this PR does / why we need it**:
The original format is very odd. So I try to fix it.
**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**:
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue
Add local volume bug to known issues
**What this PR does / why we need it**:
Update known issues with local volume issue #48331
Automatic merge from submit-queue
The first letter should be capitalized
**What this PR does / why we need it**:
The first letter should be capitalized
**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**:
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue
CHANGELOG.md: update outdated link
I am not sure that if the file was generated automatically.
But I find some links were outdated.
Release note:
NONE
Automatic merge from submit-queue
Add warning to skip v1.6.0 if you use kubeadm.
I'm not sure if this is the right place to put the warning. Suggestions welcome. Ideally it should be near the top and obvious to anyone who uses `kubeadm` but not overly obnoxious for those who don't.
Automatic merge from submit-queue
fix the anchor link
**What this PR does / why we need it**:
fix the anchor links about "kubectl rolling-update" and "kubectl delete", they did not work at present.
Automatic merge from submit-queue
Add a link to the kubeadm changelog from the main k8s changelog
@spiffxp @idvoretskyi @mikedanese @saad-ali A small addition to the changelog
Automatic merge from submit-queue
Remove a release-note on multiple OpenAPI specs
We added this feature (multiple OpenAPI specs) and then remove it while developing openAPI in 1.5. It does not make sense to have it as part changelog. The feature never been release in 1.4 or 1.5 and was only available during development of 1.5.
