The `*.profile` file referenced do not need to be provided in a separate
file. Making them separate files is preventing Hugo 0.57.2 from correctly
building the site.
This PR separates the graduated/deprecated feature gates into a separate
table. When updating the table contents by browsing the source code, we
also found some missing items which are added in this PR as well.
(cherry picked from commit faae88f478)
1. Confirm the document content is similar as en version.
2. Merge the zh release-1.14 version into 1.15 version
3. add the 1.14 all sample into 1.15 for template work. The build looks fine.
- docs
- concepts
- architecture
* Update DaemonSet deletion documentation
The "Updating a DaemonSet" section referred to pre-1.6 behavior, where
rolling updates of DaemonSets were not supported and thus orphaned pods
from deleted DaemonSets would not be replaced by a new DaemonSet.
Describe the new behavior, where orphaned pods can be adopted by a new
DaemonSet and may be replaced depending on the update strategy in use.
* Tweak language around Pod replacement after DaemonSet deletion
* Update note about DaemonSet rolling updates
No need to call out the version in which rolling updates for DaemonSets
were introduced given how long they've been supported.
* Fix title of audit task
The content the title refers to indicates an intent of describing how
to configure auditing for multiple apiservers rather than multiple
clusters.
* Update content/en/docs/tasks/debug-application-cluster/audit.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* ID translation for assign-pod-node
* fix typo
* add pods/pod-nginx.yaml example file
* add pods/pod-with-node-affinity.yaml example file
* add pods/pod-with-pod-affinity.yaml example file
* Apply suggestions from code review
Co-Authored-By: Irvi Aini <7439590+irvifa@users.noreply.github.com>
* tidy up words following code review suggestion
Add shortcode, partial, and css so we can display an accouncement
site-wide.
Create a shortcode for use in content/en/ _index.html so
announcement is displayed on website landing page.
Create a partial for use in layouts/docs/baseof.html so
announcement is displaye on every page in '<url>/docs/home'
directory.
Add two values to config.toml: announcement (boolean) for toggling
display of announcement; announcement_message, which is the actual
message.
Signed-off-by: Aimee Ukasick <aimeeu.opensource@gmail.com>
- Gardener is a fully managed service, including day-1 and day-2 operations
- Gardener supports OpenStack (and Packet Cloud), which is often the foundation for on-premise installations
See e.g. adopters like https://bnerd.com which are offering a Gardener-based fully managed Kubernetes service in their own OpenStack DCs. More information at https://github.com/gardener/gardener/blob/master/ADOPTERS.md.
* Translate `concepts/scheduling/_index.md` to Korean (#16072)
* Translate concepts/workloads/controllers/replicaset.md in Korean (#16070)
* Update outdated content in dev-1.15-ko.5 (#16162)
* Translate using-api/client-libraries into korean (#16182)
* ko: translate concepts/cluster-administration/proxies (#16030)
* Translate concepts/workloads/controllers/deployment.md in Korean (#16113)
Co-Authored-By: Seokho Son <shsongist@gmail.com>
Co-Authored-By: Eden <longlg88@naver.com>
Co-Authored-By: Yoon <learder@gmail.com>
Co-Authored-By: Sunghoon Kang <me@devholic.io>
Co-Authored-By: Yuk, Yongsu <ysyukr@gmail.com>
Co-Authored-By: June Yi <gochist@gmail.com>
This patch turns the glossary entry for "workloads" into "workload" in
order to be consistent with other terms in the glossary. In addition,
the definition is modified to match what the overlay tip for the
"Workload" tag at the top of the glossary page says, which is
"Applications running on Kubernetes".
A workload is *not* a core object itself. Rather, it is a general
concept. Various other core objects describe different types of
workloads, and the glossary definition is appropriately modified to make
that clear.
Fixes Issue #14107
- Sample CRD will not work due to apiextensions.k8s.io/v1beta1 setting preserveUnknownFields to true by default. Set to `false`.
- Provide required `type: object` at `openAPIV3Schema` root for both versions to avoid `schema.openAPIV3Schema.type: Required value: must not be empty at the root` error.
aimeeu