* Create PID Limiting Blog
Blog from Derek Carr commissioned by Kaitlyn
* Update 2019-3-28-PID-Limiting
* Update and rename 2019-3-28-PID-Limiting to 2019-03-28-PID-Limiting
* Update and rename 2019-03-28-PID-Limiting to 2019-03-28-PID-Limiting.md
* Update 2019-03-28-PID-Limiting.md
* Update 2019-03-28-PID-Limiting.md
When using udp backend, flannel uses UDP port 8285 for sending encapsulated packets.
When using vxlan backend, kernel uses UDP port 8472 for sending encapsulated packets.
Make sure that your firewall rules allow this traffic for all hosts participating in the overlay network.
Fixed the broken link for 'kubectl autoscale' in the statement - Now that the server is running, we will create the autoscaler using kubectl autoscaling.
This issue is referenced in #13683
removed hyperlink from "An example" in the statement An example of this approach is a small container running logrotate periodically. However, it's recommended to use stdout and stderr directly and leave rotation and retention policies to the kubelet.
This fix is for issue #13656
The link for one function in the line "Most of the common code are located in the framework file that leaves only one function to be implemented for different conversions" has been changed.
Resolving issue #13760
There is a line accidentally added in kubefed.md:' ###### Auto-generated by spf13/cobra on 26-Mar-2019'. This is meaningless so removing this from the page.
This also fixes#13755
* Example for injecting single secret as env variable
Define a container environment variable with data from a single Secret
* Env variable using secret data
* Update pod-single-secret-env-variable.yaml
* Adding example for multiple env variable using secrets
Adding example for multiple env variables using secrets
* Create pod-secret-envFrom.yaml
* Update pod-multiple-secret-env-variable.yaml
* Update pod-multiple-secret-env-variable.yaml
* Update pod-multiple-secret-env-variable.yaml
* Update pod-single-secret-env-variable.yaml
* Update pod-multiple-secret-env-variable.yaml
* Update pod-single-secret-env-variable.yaml
* Different ways to add env variable using secret
Adding different ways to add env variable in pod using secret
* Correcting formatting issues
Correcting formatting issues
* Correcting format issue
init index.md
cleanup main doc
[docs-fr] add introduction and A record
[docs-fr] add dns policies for pods and services
[docs-fr] fix netlify deploy error when reading yaml file
[docs-fr] fix typos according to pr review
[docs-fr] update reviewers
I've attempted to have it make more sense by removing the word 'is'. Optionally, depending on the intended meaning, the sentence could read differently by leaving the word 'is' alone and changing the word 'through' to 'though'.
In given manifest, podManagementPolicy is set as Parallel, but in later section of page, the console logs of "kubectl get pods -w -l app=zk" command displays ordered behavior, which is not the actual result in case of Parallel option.
Sample logs from doc :
NAME READY STATUS RESTARTS AGE
zk-0 0/1 Pending 0 0s
zk-0 0/1 Pending 0 0s
zk-0 0/1 ContainerCreating 0 0s
zk-0 0/1 Running 0 19s
zk-0 1/1 Running 0 40s
zk-1 0/1 Pending 0 0s
zk-1 0/1 Pending 0 0s
zk-1 0/1 ContainerCreating 0 0s
zk-1 0/1 Running 0 18s
zk-1 1/1 Running 0 40s
zk-2 0/1 Pending 0 0s
zk-2 0/1 Pending 0 0s
zk-2 0/1 ContainerCreating 0 0s
zk-2 0/1 Running 0 19s
zk-2 1/1 Running 0 40s
## here pods are created in order
Actual results after applying the given manifest :
[taher@kubernetes-docker ~]$ kubectl apply -f zookeeper.yaml
service/zk-hs created
service/zk-cs created
poddisruptionbudget.policy/zk-pdb created
statefulset.apps/zk created
[taher@kubernetes-docker ~]$ kubectl get pods -w -l app=zk
NAME READY STATUS RESTARTS AGE
zk-0 0/1 Pending 0 3s
zk-1 0/1 Pending 0 3s
zk-2 0/1 ContainerCreating 0 3s
zk-1 0/1 Pending 0 4s
zk-0 0/1 Pending 0 4s
zk-1 0/1 Pending 0 5s
zk-0 0/1 Pending 0 5s
zk-1 0/1 Pending 0 5s
zk-1 0/1 ContainerCreating 0 5s
zk-0 0/1 Pending 0 5s
zk-2 0/1 Running 0 19s
zk-1 0/1 Running 0 24s
zk-2 1/1 Running 0 35s
zk-1 1/1 Running 0 37s
## here pods are created in parallel
Resolution :
Either change the value of podManagementPolicy option to OrderedReady or remove that option, so that StatefulSet will take it's default behavior.
k8s does not support nested namespaces but this is not specified anywhere in the document. I find this is the right place to document it as we introduce namespace concept here. Also these details are important to mention specifically for users who are coming from Docker UCP background.
* fix note shortcode, lists
- fix note shortcode for use in lists
- add example in style guide
* add more items to list
* update warning, caution, minor tweaks
* more updates
* Remove enable resource quota note
As of now, `ResourceQuotaScopeSelectors` is enabled by default, since it's in beta. So, let's remove it.
* Update resource-quotas.md
vonguard
Philippe MARTIN
yanghaichao12
Karen Bradshaw
Arthur De Magalhaes
codyc
presto9292
Mumshad Mannambeth
Lubomir I. Ivanov
rishgh
manyatripathi
Vageesha17
Shifali-Srivastava
Rajesh Deshpande
Danny Berger
Zihong Zheng
Srinivas R Kulkarni
Miguel Angel Medina Mondragon
Song Kun
Enrique Medina Montenegro
Shuang Wang
Gasmi Christophe
Roy Lenferink
Michele Berardi
Amina Waddiz
Paul Roth
Jan Dolecek
Nishanth Reddy
Diego Muñoz Escalante
Andrew Sy Kim
makocchi
RA489
Taher Bohari
Michael Michael
Luc Perkins
Daniel Lipovetsky
Subrata Paul
Ricardo Cordeiro
Chas Schley
Marc Sensenich
Supriya Sirbi
goodluckbot
Abhishek Jaisingh
Himanshu Pandey
Kaitlyn Barnard
RaviSantosh Gudimetla
Claudia J.Kang
Shashank Patel
zhangqx2010
Zhimin Wu
Nick Veitch
AJ Moore
Zach Corleissen
Ismail Alidzhikov
Manuel Rüger
AbdullahBM
Tennis Smith
Joseph Heck
Alex Contini
ethan
Blade
Benedikt Rollik
Rémy Léone