* How You Can Help Localize Kubernetes Docs
Minor edits
Minor edits
Publish for 25 Apr
One typo
* Update 2019-04-25-latest-on-localization.md
* Update and rename 2019-04-25-latest-on-localization.md to 2019-04-26-latest-on-localization.md
* Delete all pods matching the egrep pattern
* replace egrep with awk to delete pods by a pattern
* Update content/en/docs/reference/kubectl/cheatsheet.md
Co-Authored-By: ismailyenigul <ismailyenigul@gmail.com>
I thought this organization would give the users a better idea of what method to select based on the OS they use.
Initially, I was a wee bit confused when I saw how to Install kubectl binary with curl on the Mac OS and then another section on how to install Kubectl on the Mac OS.
Now, I moved the content under the $subject to the respective OS section.
P.S: I am still in the process of testing out the steps. :)
* Blog post: Hardware Accelerated Crypto...
This adds a story of Hardware Accelerated SSL/TLS Termination
in Ingress Controllers using Kubernetes Device Plugins and RuntimeClass.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
* Update Hardware-Accelerated-SSLTLS-Termination-in-Ingress-Controllers-using-Kubernetes-Device-Plugins-and-RuntimeClass.md
* Rename Hardware-Accelerated-SSLTLS-Termination-in-Ingress-Controllers-using-Kubernetes-Device-Plugins-and-RuntimeClass.md to 2019-04-23-Hardware-Accelerated-SSLTLS-Termination-in-Ingress-Controllers-using-Kubernetes-Device-Plugins-and-RuntimeClass.md
* Rename 2019-04-23-Hardware-Accelerated-SSLTLS-Termination-in-Ingress-Controllers-using-Kubernetes-Device-Plugins-and-RuntimeClass.md to 2019-04-24-Hardware-Accelerated-SSLTLS-Termination-in-Ingress-Controllers-using-Kubernetes-Device-Plugins-and-RuntimeClass.md
Plain language rocks
Remove an orphaned line
Remove note
Present tense rocks
Add repository
Feedback, round 1
Add team descriptions
Add Slack link
Feedback, part 2
Feedback from gochist
Remove link
* Revise guide for generating reference docs
This PR changes the guidance for generating reference documentation for
Kubernetes API and kubernetes components. The topic of making changes to
the upstream repo is separated out because 1) it is not a mandatory step
for generating the reference docs; 2) it is about a more advanced level
of documentation fix.
* light copyedit
* more light copyedits
* updated link for framework file
Fixed the invalid link referred by "framework file" in "Most of the common code are located in the framework file that leaves only one function to be implemented for different conversions.".
This fix is for the issue #13759 .
* updated framework file link reference to v1.14
changed docs version from v1.13.0 to v1.14.0 in the link reference
"framework file" -> https://github.com/kubernetes/kubernetes/tree/v1.14.0/test/images/crd-conversion-webhook/converter/framework.go
Changes the key name to `SPECIAL_LEVEL` in the config map volume definition.
This is consistent with the rest of the example. Otherwise, this pod does not
start because there is no key with that name in the `special-config` config map.
* Add formal definition of workloads
* Update workload.md
* add light copyedit
More section should not repeat short description. Both are served together on the built page.
These statement was intended to specify environment variable values available in the container but word 'environment variable' was missing so corrected these statements for better clarity.
fixed the invalid link referred by "this guide" in "In Kubernetes v1.11.0 and later, you can use kubeadm upgrade diff to see the changes that would be applied to static pod manifests."
this is fix for issue #13869
* fixed the broken link
Fixed the broken link for CDK official documentation.
Resolving the issue #13820
* fixed broken link
made few changes required for the issue #13820
* fix an offense against the style guide.
> Refer to API objects without saying “object,” unless omitting “object” leads to an awkward construction.
* fix another one.
* [WIP] Clean up kubectl install page
Fixes issue #13577
* Update install-kubectl.md
Addresses @zacharaysarah and @jaredbhatti's comments.
Minor language Improvements:
- Deleted unnecessary adverbs
- Used fewer words where possible
Next pass will include deeper edits, with careful attention to the kubectl autocompletion section
* Update install-kubectl.md
* 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
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
Alex Contini
Jared
chenrui
silenceshell
codyc
Chris Abraham
Zach Corleissen
Nikhita Raghunath
Damini Satya
Yecheng Fu
王(Wang)
Stephen Augustus
ismail yenigul
shavidissa
Guy Templeton
Danny Berger
WanLinghao
Yuchen
Mikko Ylinen
Kibo Hikari
Milo Hartsoe
Lubomir I. Ivanov
Qiming
Brandon Philips
Jason L. van Brackel
shub-asa1
Saifuding Diliyaer
Dani Comnea
Julio Lopez
RA489
Tim Bannister
Joseph Irving
Rajesh Deshpande
giri
Vageesha17
makocchi
Kaitlyn Barnard
Andrew Sy Kim
Christoph Stäbler
Cody Clark
vonguard
yanghaichao12
Karen Bradshaw
Arthur De Magalhaes
presto9292
Mumshad Mannambeth
rishgh
manyatripathi
Shifali-Srivastava
Danny Berger
Zihong Zheng
Srinivas R Kulkarni
Miguel Angel Medina Mondragon
Song Kun
Paul Roth
Jan Dolecek
Nishanth Reddy
Taher Bohari
Michael Michael
Luc Perkins
Daniel Lipovetsky
Subrata Paul
Ricardo Cordeiro
Chas Schley
Marc Sensenich
Supriya Sirbi
goodluckbot
Abhishek Jaisingh
Himanshu Pandey
RaviSantosh Gudimetla
Shashank Patel