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.
Since minikube v0.33.0 the default CNI config is not being provisioned
by default (https://github.com/kubernetes/minikube/pull/3441). Therefore,
we need to pass `--enable-default-cni` when starting minikube.
There is output of `kubeadm init` in create-cluster-kubeadm page.
But it is little old.
Some processes aren't included in it.
This update `kubeadm init` output to latest.
Since Kubernetes 1.10, the only supported CRI version is v1alpha2. However,
rktlet does not support that version and development seems stopped.
As there is no way to use rktlet with k8s >= 1.10, it's best to just remove
the rkt link from the "Install runtime" section of "Install kubeadm".
Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
* kubeadm: add a caution about certs in HA document
* Update content/en/docs/setup/independent/high-availability.md
Co-Authored-By: neolit123 <neolit123@gmail.com>
If there is a combination of `systemctl` commands where in one you are
enabling it and in another you are starting it, that can be done in one
single command with an additional flag called `--now`. This commit
changes those two command steps in docs to one command.
The help of systemctl shows the following explanation of `--now`:
```
Start or stop unit in addition to enabling or disabling it
```
Signed-off-by: Suraj Deshmukh <surajd.service@gmail.com>
* Add `jsonpath` approach for apiserver query
* Refine the wording with the approach description
* Refine the command log
* Move the itemized number back
Added VMware Cloud PKS and Cloud Foundry Container Runtime to places within the document that are correctly represented for Cloud and on-primises offerings and tooling. I also properly alphabetized the list.
Signed-off-by: Kendrick Coleman <kendrickc@vmware.com>
The "Assigning Pods to Nodes" page did not mention nodeName, which, if
specified, takes priority over the methods discussed in the page. Add
description of nodeName and an example using it.
Address reviewer comments from @bsalamat and @liggitt, thanks!
Naoki Oketani
Damini Satya
PingWang
Tim Bannister
Tomas Kral
Andrew
Nick Veitch
Yu-Zhen Tu
Matt McNaughton
Brendan Wrafter
Jérémy Mathevet
Lubomir I. Ivanov
Carston Schilds
ethan
Florian Breisch
Alex Gervais
lIuDuI
Zach Corleissen
Kaitlyn Barnard
ROY
Marcin Kłopotek
Stacy Pedersen
Noah Kantrowitz
Seokho
Daniel Bryant
Evan
Himanshu Pandey
Slava Semushin
Vineeth Reddy
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
O'meid
Martynas Pumputis
Jun Gong
Barnabas Makonda
R
atoato88
Mumshad Mannambeth
Wenjun Wu
Rostislav M. Georgiev
yanghaichao12
Roy Lenferink
Jai
Kenichi Omichi
SalimGangji
Claudia J.Kang
Avi Deitcher
James Ward
Anuj Sharma
joao brito junior
Dr Luke Angel
Suraj Deshmukh
craigbox
azarnyx
chenrui
Kendrick Coleman
Jintao Zhang
David Dooling