* Rename `docs/concepts/scheduling` to `docs/concepts/scheduling-eviction`
* Retitle concept header to "Scheduling and Eviction"
* Update redirects
* Update internal links (en only)
Part of proposal #19081
Signed-off-by: Adam Kaplan <adam.kaplan@redhat.com>
Translate hyperlinks
Fix nits:
+ leftover translation
Nits:
+ unitalicize k8s resource
+ replace trafik
Nits:
+ remove reviewers
+ correct Endpoint to Endpoints
+ remove {#endpointslice-resource}
+ translate the word flag
Nits:
+ uncapitalize selector
Update on suggestions:
+ daripada -> terhadap
+ performa -> kinerja
+ translate subdomain name
+ translate default
+ rephrasing
Updates on reviews and suggestions:
+ translate scalable
+ replace serangkaian to sekumpulan
+ use diasosiasikan instead of terasosiasi
+ use diikutinya to translate track
+ replace mengkonfigurasi with mengatur
+ treat EndpointSlices as singular
Fix leftover word
Nits:
+ unitalicize platform
+ use selektor instead of selector
Nits:
+ translate rolling update
+ use cukup instead of sangat
+ translate repacking
Topology Manager deal with Guaranteed QoS Pod.
=>Topology Manager deal with all Pod QoS Classes since 1.17
Topology Manager works on Nodes with the Static CPU Policy enabled
=> changing wording to make this clearer and adding examples
Signed-off-by: Byonggon Chun <bg.chun@samsung.com>
The timezone for the kube-controller-manager (or if that's broken apart,
the cronjob controller) determines when CronJobs are scheduled.
This reverts commit bad124b857.
Reword Pod readiness section
- “Pod Ready++” is stable, so word the documentation accordingly.
- In the documentation, call this “Pod readiness”
- Related tweaks
Reword Pod lifetime section
- mention StatefulSet
- omit mentioning ReplicationController as it's deprecated
- reword to suggest that the list of workload resources is non-exhaustive
and use glossary tooltips as well.
* Currently documentation mentions resolvable FQDNs for services only
* Documentation for pods is confusing in regards of local pod `hostname`
wich actually does not match in-cluster DNS resolution
* This PR clarifies FQDN schema that is used for pod DNS resolution
Kubernetes Prow Robot