* Add Pod Disruption Budget to Glossary
* Update content/en/docs/reference/glossary/pod-disruption-budget.md
Cross referenced Pod term
Co-Authored-By: McCoyAle <mccoyale@gmail.com>
* Update pod-disruption-budget.md
* Add cross-namespace service account example, clarify binding wording
* Add create role and create clusterrole help
* Add reconcile documentation
* Document roleRef restrictions
- Use “Job” to mean the Kubernetes object
- Use “job” where capitalization hinders readability
- Use “task”, or other synonymous concepts, to avoid confusion
- Use “Pod” to mean the Kubernetes object
- Use “pod” where capitalization hinders readability
- Use “container” in lowercase everywhere
Also:
- Clarify work queue example for Job controller
- Fix advice on running Job example
- Tweak emphasis
* Use glossary terms when explaining Secret concept
* Tidy up advice on keeping Secrets secret
* Reformat note on how Secrets are displayed
* Use mebibytes
* Update network doc for ip-per-pod reqs
As per SIG-Network discussion, we can relax the requirement for all
nodes to be able to reach all pods on those platforms that do not
support hostNetwork.
The current thinking on Windows support is that hostNetwork is not a
requirement for Window users. As such, satisfying the old requirement
is very difficult and has no practical benefit.
This DOES NOT change the requirements for platforms that support
hostNetwork (e.g. Linux) nor does it make hostNetwork optional for Linux
nodes.
This PR also removes most comparisons to Docker, as they are stale and
no longer germane, and cleans up some of the text.
* Feedback on contents
* setup/cri: add a section about cgroup drivers
A cgroup driver is an important setting for the CRI and the kubelet.
Add a section that explains why "systemd" is the suggested value
for a driver when installing a CRI.
In the case of Docker the kubelet will receive this value automatically.
For the other CRIs, the users should tackle this manually.
* Update cri.md
* Update building-from-source.md
Update the page to be consistent with the concepts template.
* Update building-from-source.md
Update the page to be consistent with the concepts template.
It looks like `nginx -s quit` returns immediately rather than blocking until nginx has finished gracefully shutting down. As a result, just running `nginx -s quit` in the preStop hook won't work very well for high load and/or long running requests; nginx will get a TERM signal (and do a hard shutdown) immediately after `nginx -s quit` returns.
(I was getting connection errors while terminating pods, and adding a sleep-until-done to the preStop hook seemed to make them go away.)
* Add service path to CRD webhook conversion example
* Update wording in CRD conversion example to indicate it is serving traffic
Co-Authored-By: nrfox <nickfox25@gmail.com>
The changes are in line with one of the request for documentation update as per PR #55807 wherein it was observed that the preStop hook is not commissioned when the container is already in the terminated or completed state.
Braces removed as per the review comment. Multiple commits squashed
Braces removed as per the review comment
Update as per review, removed etc... and the statement is now cleaner
* Disruptions: make clearer not all voluntary disruptions are constrained by PDBs
Currently, there's confusion on whether all voluntary disruptions are constrained by PDBs.
For example, see the three comments [here](https://github.com/kubernetes/kubernetes/issues/39824#issuecomment-436322189).
* Update content/en/docs/concepts/workloads/pods/disruptions.md
Co-Authored-By: davidxia <davidxia@users.noreply.github.com>
* Update content/en/docs/concepts/workloads/pods/disruptions.md
Co-Authored-By: davidxia <davidxia@users.noreply.github.com>
* Update disruptions.md
* Alias for kubectl with completion.
Use a shorthand alias for `kubectl` that also works with completion. Using completion is great but typing `kubectl` each time is annoying.
* Update content/en/docs/reference/kubectl/cheatsheet.md
Co-Authored-By: jogy <johann@gyger.name>
* Update AKS mitigation link
Updated to include link to AKS documentation on mitigation.
* Updated Microsoft Recommendation
Updated with suggested changes
Address the issue raised in
https://github.com/kubernetes/kubernetes/issues/73808, where it became
clear it would be helpful for there to be a reminder for the user that
they are responsible for managing the StatefulSet which provides DNS
names for the pods in a StatefulSet.
Cleaned up the section __Revision History Limit__ to reflect the default value of `.spec.revisionHistoryLimit` being 10, instead of saying "All old ReplicaSets will be kept by default"
* Adding proposed blog post for building-a-kubernetes-edge-control-plane-for-envoy-v2
* Update article with improvements and author list
* Update and rename building-a-kubernetes-edge-control-plane-for-envoy-v2.md to 2019-02-11-building-a-kubernetes-edge-control-plane-for-envoy-v2.md
* Add extra coverage about use of Golang in Ambassador 0.50
* Minor typo fixes
* Minor typo fix, and merge fix with date
* Update 2019-02-11-building-a-kubernetes-edge-control-plane-for-envoy-v2.md
* Delete building-a-kubernetes-edge-control-plane-for-envoy-v2.md
* Update 2019-02-11-building-a-kubernetes-edge-control-plane-for-envoy-v2.md
* First pass on a blog post about CVE-2019-5736.
* Clarify that k8s is not the problem.
* Fix example of pinning to an image hash.
My mistake deftly caught by @zparnold.
Co-Authored-By: coderanger <noah@coderanger.net>
* Add links to the rest of the notices or releases.
* Add ways to get more info.
* RHEL link for those that don't selinux.
* Link to Rancher's back ports.
* Adding container state details in documentation
* Adding container state details to documentation
* Incorporating changes suggested in review by /ryanmcginnis
The binaries themself indicate:
```
--windows-service Enable Windows Service Control Manager API integration
```
It also doesn't appear to have changed, since it's like this since this landed:
4ea363d98e (diff-34a9920a4db69d1542b66bcb6fe4ac1eR39)
Possibly an oversight after changing it before the merge.
This ensures the documentation is consistent with the code and help outputted by kubernetes binaries again.
/sig windows
* First draft of the updates to the ReplicaSet Docs
To start with, I tried to cleanup the docs to adhere to the style guide https://kubernetes.io/docs/contribute/style/style-guide/. I then added some description of the ReplicaSet-Pod link via the owner reference field and behavior by it. I also made a clarification on the ReplicaSet demo where it was being redundant for the sake of demonstrating the different forms of usage. I consider this draft incomplete as I still lack knowledge of how the pod labels affect the behavior.
* Clearing up RC refs & explaining acquisition behavior
I'm beginning to address the cr by cleaning up references to the ReplicationController and making it clear that RCs are discouraged/old. I then expanded on the behavior of ReplicaSet in the presence of pods it can acquire but are not created directly by it.
* Mismatched link seems to have disappeared from preview
"As with all other Kubernetes API objects," etc... is present in the sibling concepts/workloads/controllers/ files, so I am hesitant to change that w/o changing the others, but I did abbreviate it.
"The `.spec.template` is the only required field of the `.spec`." is false, we also need the selector
Trying to address passive voice
Cleaned up Writing a ReplicaSet Manifest section
removed How to use a ReplicaSet section as it has redundant info from the examples and Alternatives section
Expanded examples a bit
Cleared up passive voice
* refactoring link to example yaml
* adding pod-rs test case
* Addressing Steve Perry's comments
Capitalize Pod throughout.
Link is not rendering correctly. Use () instead of [] for the path.
Ending with "for the creation" seems vague to me. Maybe this:
"...reach the desired number. When a ReplicaSet needs to create new Pods, it uses its Pod template."
Suggestion: "is via the Pod's metadata.ownerReferences field." That way the reader won't jump to the incorrect conclusion that we're talking about the ReplicaSet's metadata.ownerReferences field.
with fields, including a selector that
and plans accordingly
Our style for headings is sentence case. So this heading would be "How a ReplicaSet works".
Several headings in this topic need to be converted to sentence case.
cleaned up frontend.yaml example
added example checking the Pod's owner reference being set to it's parent ReplicaSet
* Previous commit broke Pod example links due to casing
* Forgot 1 comment
Suggestion: In the ReplicaSet, .spec.template.metadata.labels must match spec.selector, or ...
* Addressing grammar/syntax errors
* Blog post for Poseidon-Firmament Scheduler
* Fixed some typos. Fixed some formatting. Added links.
* Update and rename 2019-02-04-poseidon-firmament-scheduler-announcement.md to 2019-02-06-poseidon-firmament-scheduler-announcement.md
* Made some changes to the Key Advantages section.
McCoyAle
Jordan Liggitt
Avi Deitcher
Tim Bannister
Dr Luke Angel
Tim Hockin
Lubomir I. Ivanov
Andrew Sy Kim
Bill Mulligan
Dan Pastusek
Dario Maiocchi
Vineeth Reddy
Ben Kuhn
cell13
Nick Fox
Vinodh N
Murcurio
David Xia
Jesse Glick
hidekazuna
Johann Gyger
WanLinghao
Supriya Sirbi
shutefan
Dave Strebel
André Martins
Himanshu Pandey
Karen Bradshaw
Omid Raha
Bob Killen
Janet Kuo
Naoki Oketani
Damini Satya
PingWang
Tomas Kral
Andrew
Nick Veitch
Yu-Zhen Tu
Matt McNaughton
Brendan Wrafter
Jérémy Mathevet
Carston Schilds
ethan
Florian Breisch
Alex Gervais
lIuDuI
Zach Corleissen
Kaitlyn Barnard
ROY
Marcin Kłopotek
Stacy Pedersen
Noah Kantrowitz
Seokho
Daniel Bryant
Evan
Slava Semushin
Zhou Peng
rajeshdeshpande02
Steffen Butzer
Kanshi
Hongbin Mao
Juan Diego Palomino
Dan Kohn
Anvith KS
Hanno Kolvenbach
garlicFrancium
Scott Brenner
Manjunath A Kumatagi
Harshagarwal19
Irfan Ur Rehman
Andy Randall