There are many YAML manifests sneaking into the `zh/docs/` directory.
These files should go to the `zh/examples` directory instead. Having
these "garbage" files (not referenced anywhere) is creating confusion
for the release meister when merging branches. For example, some YAML
files found in the 'master' branch are no longer there in the
release-1.16 branch. It is tedious, if possible at all, to solve all
this kind of conflicts during a rebase.
The PR cleanses the zh/docs directory for all dangling YAML files.
* initial commit
* promote AWS-NLB Support from alpha to beta (#14451) (#16459) (#16484)
* 1. Sync release-1.15 into master
2. Sync with en version
* 1. Add the lost yaml file.
* Update he cluster administration folder of concepts
1. Sync with 1.14 branch
2. Sync with en version
* Add yaml files which are used
* 1. Sync the configuration folder from 1.14 version
2. Sync the configuration folder files with en version
3. Changed some files structure for easily review
4. Add glossary folder for fixup build error
* 1. Sync the storage folder from 1.14 version
2. Sync the storage folder files with 1.16 version en document
3. Changed some files structure for easily review
* 1. Sync the service-networking folder from 1.14 version
2. Sync the service-networking folder files with 1.16 version en document
3. Changed some files structure for easily review
4. Add the necessary documents
5. Add the runtime-class file
* initial commit
* promote AWS-NLB Support from alpha to beta (#14451) (#16459) (#16484)
* 1. Sync release-1.15 into master
2. Sync with en version
* 1. Add the lost yaml file.
* Update he cluster administration folder of concepts
1. Sync with 1.14 branch
2. Sync with en version
* Add yaml files which are used
* 1. Sync the configuration folder from 1.14 version
2. Sync the configuration folder files with en version
3. Changed some files structure for easily review
4. Add glossary folder for fixup build error
* 1. Sync the storage folder from 1.14 version
2. Sync the storage folder files with 1.16 version en document
3. Changed some files structure for easily review
* initial commit
* promote AWS-NLB Support from alpha to beta (#14451) (#16459) (#16484)
* 1. Sync release-1.15 into master
2. Sync with en version
* 1. Add the lost yaml file.
* Update he cluster administration folder of concepts
1. Sync with 1.14 branch
2. Sync with en version
* Add yaml files which are used
* 1. Sync the configuration folder from 1.14 version
2. Sync the configuration folder files with en version
3. Changed some files structure for easily review
4. Add glossary folder for fixup build error
* initial commit
* promote AWS-NLB Support from alpha to beta (#14451) (#16459) (#16484)
* 1. Sync release-1.15 into master
2. Sync with en version
* 1. Add the lost yaml file.
* Update he cluster administration folder of concepts
1. Sync with 1.14 branch
2. Sync with en version
* Add yaml files which are used
* initial commit
* promote AWS-NLB Support from alpha to beta (#14451) (#16459) (#16484)
* 1. Sync release-1.15 into master
2. Sync with en version
* 1. Add the lost yaml file.
1. Replace net.ipv4.route.min_pmtu with net.core.somaxconn in the
example of using unsafe sysctls in containers, since the former is not
accessible within container namespace at all.
2. Not all net.* sysctls are namespaced. Explain the correct way to
identify the namespaced networking sysctls.
This patch swaps all uses with extensions/v1beta1 with the new
networking.k8s.io/v1beta1 apiVersion for the Ingress resource.
Signed-off-by: Christopher M. Luciano <cmluciano@us.ibm.com>