* Prevent hugo's wrong yaml rendering
* moved a couple of yaml descriptions to examples directory
* remove command prompt
* split each code snippet into command and output
* revert newline character
* add new test in examples_test.go
* change kind to ResourceQuota from List
* revert using examples/quota-objects-priority.yaml
* fix indent number
* unify file extension to yaml
* Added shortcode callouts and removed future tense
* Added colons according to the style guide
* Add a few more copyedits
@cody-clark inspired me. More to do, but progress is being made!
The ordered list of content under "Creating a Deployment" was not ordered as per the example. Since it was confusing to search for the meaning around, I reordered the content.
Replaced "we" with "you" as per the style guide.
* Generically refer to container runtimes.
Update nodes.md to refer to "container runtimes" instead of identifying Docker specifically.
* Update nodes.md link for Container Runtime to be relative to the domain.
* Update nodes.md
Technically speaking SRV targets are address record names, not CNAMEs. In fact, the SRV RFC states that SRV targets must point to an address record name, and cannot be an alias (e.g. CNAME).
* Add debugging information to Pod priority and preemption
* mdformat the page
* keep feature-state shortcodes together
* Add one more potential bug in preemption
* Addressed reviewer comments
* Updated dns-pod-service.md
Added a note on A records creation
* Updated dns-pod-service.md
Added Hugo {{ note }} shortcode
* Update dns-pod-service.md
Changed wording
* tighten up the wording
Merging these two paragraphs, which both describe the fields included in the PodConditions. The first one mentions 6 fields, but only defines 3 of them. The second one defines two of the remaining three. The missing 6th element ("reason") has been added. Now we have the full list in one single section. Easier to understand.
* Update cron-jobs.md
Removed bullet point indicating that a `CronJob` can run "Once at a specified point in time", since this use case is either not possible, or not documented at all.
* change wording
previous document suggests to put config to /root/.docker/config.json
which is not always the case, and only works when the HOME=/root is
set for kubelet. Besides, that's not always the most recommended way
considering the potential risk when someone overrides this config
with another `docker login` on the same node. this change explicitly
lists all the possible locations where the configuration can be put.
* Update references to Federation-v2 progress
Added resources to the whats next section as there has been significant progress over the past few months with the alpha release of Federation-v2 expected in the next few weeks.
* remove <federation> in link
* update admission-controller links
(cherry picked from commit 37043991a61e5e6f4ac1c463b14c65430b192553)
* updated links found using greedier regex
(cherry picked from commit 45c6d4cf7430245a3b4e81eae245000beea88841)
* correct link in cn/docs/admin/authorization/_index.md
* fix incorrect changes introduced in eac3619
* undo update of cn content
* fix link
* fix admission webhook link
tanshanshan
makocchi
krmayankk
Qiming
Cody Clark
Lion-Wei
David Glasser
shavidissa
Nikhita Raghunath
AdamDang
Sam Foo
Slava Semushin
Takumasa Ochi
Michael Mackend
Bobby (Babak) Salamat
Karen Bradshaw
Peter (XiangPeng) Zhao
JasperTimm
Sebastiaan van Steenis
Georgios Andrianakis
WanLinghao
chenhuan
Chris O'Haver
CaoShuFeng
Vikas Choudhary (vikasc)
Suracheth Chawla
Michael
Denis Salamanca
Alfonso Palacios
michael saenz
Eric Staples
Faisal Memon
csskuber
zhouhaibing089
Luc Perkins
Lindsey Tulloch
Hesham Massoud
p_mx
Bob Killen