Both local and pod port number are same i.e. 6379 which causes confusion to first time reader. This can be easily avoided by using two different port number.
* Correcting order of display for daemon set tasks
Correcting order of display for daemon set tasks
* Correcting display order of daemon set task
Correcting display order of daemon set task
here apt installs both kubelet and kubectl but just holds kubelet. I think kubectl should alse be held by apt-mark.
```
# replace x in 1.14.x-00 with the latest patch version
apt-mark unhold kubelet && \
apt-get update && apt-get install -y kubelet=1.14.x-00 kubectl=1.14.x-00 && \
apt-mark hold kubelet
```
Add meeting guidelines, graphic
Update embedded image
Use raw HTML for image link
Edit path
Indent list items
minor edits
Add line breaks for indentation
Add bolding
Add section for meetings
Feedback from jimangel
* Use glossary references where appropriate
* Link from Pod overview to detailed Pod concept
* Assume that privileged containers are stable
* Improve wording
* Write Pod in upper case
As Pod is an API object, write it in upper case.
This patch swaps all uses with extensions/v1beta1 with the new
networking.k8s.io/v1beta1 apiVersion for the Ingress resource.
Signed-off-by: Christopher M. Luciano <cmluciano@us.ibm.com>
* Define SLO acronym
Save people from having to search for the translation of SLO to Service-Level Objectives.
* replace SLO with direct PodDisruptionBudget reference
The orders of kind and metadata were inconsistent, and that made the
doc unreadable.
This fixes the orders in consistent way under pods/init-containers.md.
* updated self-hosting documentation
* removed more referances
* updated wording
* updated self-hosting warning to be more clear about the effects of pivot has on your cluster
* Update content/en/docs/setup/independent/self-hosting.md
Co-Authored-By: Klaven <mcounts@suse.com>
*minikube ssh* logs into the cluster as user 'docker'. The user 'docker' (uid=1000) does not have write permissions in /mnt to create a new directory and/or the example's HTML file. Use sudo(8) to create the directory as well as the HTML file nginx will ultimately serve.
* Fix broken link in service-accounts-admin.md
a213182b10
added a linke to [projected volume] that maybe got renamed.
* Update service-accounts-admin.md
Added steps to find out if virtualization in installed on the users OS.
Minor improvement
Capitalized Windows
Removed the shell from the command.
Update install-minikube.md
by kubectl apply.
The docs imply that lists whose elements are all primitives
are replaced by the applied config instead of being updated.
This PR states that explicitly for clarity.
* Add files via upload
KubeCon Barcelona 2019 Diversity Lunch & Hack Blog Post
* Update 2019-04-25-kubecon-diversity-lunch-and-hack.md
* Update and rename 2019-04-25-kubecon-diversity-lunch-and-hack.md to 2019-05-02-kubecon-diversity-lunch-and-hack.md
* adding Elastic Stack for logging and monitoring
* added section on deploying Elasticsearch and Kibana
* more detail
* more detail
* First draft
* Using tutorial template.
* more goodness
* Describe autodiscover
* added verification steps
* Added cluster role binding
* Use Redis metrics and logs
* cleanup
* add cleanup
* unused
* Added language tags
* Added glossary_tooltip
* Added link
* Placed alternative steps in tabs
* shorten heading
* uppercase for Kubernetes objects
* cleanup secret
* grammar
* updated title and linked from the guestbook tutorial
* added reviewer. Thanks Tim!
* Removed default username/password
* typo, verbosity, more info.
`CPUCFSQuotaPeriod` Feature Gate is set from the flag name `CustomCPUCFSQuotaPeriod` per [`kube_features.go#163`](https://github.com/kubernetes/kubernetes/blob/master/pkg/features/kube_features.go#L163)
This PR updates the docs to suit.
In some respects it would be tidier to remove `Custom` prefix from `kube_features.go` so that the Feature Gate naming maps 1:1.
Happy to close this PR and do PR to remove 'Custom' prefix instead.
Added a step under the sections that guide the user to install the binary using curl on the OS. This is the same format maintained by the other section on this page.
* Add Setting up the OWNERS files section
* Update OWNERS_ALIASES patch
* Replace owners.md link with go.k8s.io/owners
* Replace github.com/kubernetes link with git.k8s.io
* Update OWNERS_ALIASES to use git.k8s.io link
* Sort patch diff in alphabetical order
* Specify clearly what teams should be added
* Remove the passive voice
* Complete alphabetical order phrase
* 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
* Connection reset blog post
* Update and rename 2019-03-27-kube-proxy-subtleties-debugging-an-intermittent-connection-resets.md to 2019-03-29-kube-proxy-subtleties-debugging-an-intermittent-connection-resets.md
* blog post on Minikube
* Updates
* Update 2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
* Update 2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
* Fix StorageObjectInUseProtection format in doc
Fix StorageObjectInUseProtection format to follow other admission controllers in doc.
* remove {#storageobjectinuseprotection}
* Correcting statement about Service ports
Correcting details about service ports and protocol. Removed statement saying Service supports the single port definition only and added details about multiport definitions.
* Correcting format changes
Correcting format changes as per feedback from reviewer.
This patch adds a entry in the kubeadm troubleshooting guide
about a problem that was found some time ago related to
kube-proxy DaemonSets and worker nodes in a CP setup.
* Official documentation on Poseidon/Firmament, a new multi-scheduler support for K8S. (#11752)
* Added documentation about Poseidon-Firmament scheduler
* Fixed some style issues.
* Udpated the document as per the review comments.
* Fixed some typos and updated the document
* Updated the document as per the review comments.
* Document timeout attribute for kms-plugin. (#12158)
See 72540.
* Official documentation on Poseidon/Firmament, a new multi-scheduler (#12343)
* Removed the old version of the Poseidon documentation. Incorrect location.
* Official documentation on Poseidon/Firmament, a new multi-scheduler support for K8S (#12069)
* Official documentation on Poseidon/Firmament, a new multi-scheduler support for K8S. (#11752)
* Added documentation about Poseidon-Firmament scheduler
* Fixed some style issues.
* Udpated the document as per the review comments.
* Fixed some typos and updated the document
* Updated the document as per the review comments.
* Updated the document as per review comments. Added config details.
* Updated the document as per the latest review comments. Fixed nits
* Made changes as per latest suggestions.
* Some more changes added.
* Updated as per suggestions.
* Changed the release process section.
* SIG Docs edits
Small edits to match style guidelines.
* add plus to feature state
* capitalization
* revert feature state shortcode
since this is a Kubernetes extension, not a direct feature, it shouldn't use the regular feature state tagging.
(cherry picked from commit 7730c1540b)
* Remove initializers from doc. It will be removed in 1.14 (#12331)
* kubeadm: Document CRI auto detection functionality (#12462)
Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
* Minor doc change for GAing Pod DNS Config (#12514)
* Graduate ExpandInUsePersistentVolumes feature to beta (#10574)
* Rename 2018-11-07-grpc-load-balancing-with-linkerd.md.md file (#12594)
* Add dynamic percentage of node scoring to user docs (#12235)
* Add dynamic percentage of node scoring to user docs
* addressed review comments
* delete special symbol (#12445)
* Update documentation for VolumeSubpathEnvExpansion (#11843)
* Update documentation for VolumeSubpathEnvExpansion
* Address comments - improve descriptions
* Graduate Pod Priority and Preemption to GA (#12428)
* Added Instana links to the documentation (#12977)
* Added link to the Instana Kubernetes integration
* Added Instana link for services section
Added Instana and a link to the Kubernetes integration to the analytics services section and broadened the scope to APM, monitoring and analytics.
* Oxford comma /flex
* More Oxford commas, because they matter
* Update kubectl plugins to stable (#12847)
* documentation for CSI topology beta (#12889)
* Document changes to default RBAC discovery ClusterRole(Binding)s (#12888)
* Document changes to default RBAC discovery ClusterRole(Binding)s
Documentation for https://github.com/kubernetes/enhancements/issues/789 and https://github.com/kubernetes/kubernetes/pull/73807
* documentation review feedback
* CSI raw block to beta (#12931)
* Change incorrect string raw to block (#12926)
Fixes#12925
* Update documentation on node OS/arch labels (#12976)
These labels have been promoted to GA:
https://github.com/kubernetes/enhancements/issues/793
* local pv GA doc updates (#12915)
* Publish CRD OpenAPI Documentation (#12910)
* add documentation for CustomResourcePublishOpenAPI
* address comments
fix links, ordered lists, style and typo
* kubeadm: add document for upgrading from 1.13 to 1.14 (single CP and HA) (#13189)
* kubeadm: add document for upgrading from 1.13 to 1.14
- remove doc for upgrading 1.10 -> 1.11
* kubeadm: apply amends to upgrade-1.14 doc
* kubeadm: apply amends to upgrade-1.14 doc (part2)
* kubeadm: apply amends to upgrade-1.14 doc (part3)
* kubeadm: add note about "upgrade node experimental-control-plane"
+ add comment about `upgrade plan`
* kubeadm: add missing "You should see output similar to this"
* fix bullet indentation (#13214)
* mark PodReadinessGate GA (#12800)
* Update RuntimeClass documentation for beta (#13043)
* Update RuntimeClass documentation for beta
* Update feature gate & add upgrade section
* formatting fixes
* Highlight upgrade action required
* Address feedback
* CSI ephemeral volume alpha documentation (#10934)
* update kubectl documentation (#12867)
* update kubectl documentation
* add document for Secret/ConfigMap generators
* replace `kubectl create -f` by `kubectl apply -f`
* Add page for kustomization support in kubectl
* fix spelling errors and address comments
* Documentation for Windows GMSA feature (#12936)
* Documentation for Windows GMSA feature
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Enhancements to GMSA docs
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Fix links
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Fix GMSA link
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Add GMSA feature flag in feature flag list
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Relocate GMSA to container configuration
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Add example for container spec
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Remove changes in Windows index
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Update configure-gmsa.md
* Update configure-gmsa.md
* Update configure-gmsa.md
* Update configure-gmsa.md
* Rearrange the steps into two sections and other edits
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Fix links
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Add reference to script to generate GMSA YAMLs
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Some more clarifications for GMSA
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* HugePages graduated to GA (#13004)
* HugePages graduated to GA
* fixing nit for build
* Docs for node PID limiting (https://github.com/kubernetes/kubernetes/pull/73651) (#12932)
* kubeadm: update the reference documentation for 1.14 (#12911)
* kubeadm: update list of generated files for 1.14
NOTE: PLACEHOLDERS! these files are generated by SIG Docs each
release, but we need them to pass the k/website PR CI.
- add join_phase* (new sub phases of join)
- add init_phase_upload-certs.md (new upload certs phase for init)
- remove alpha-preflight (now both init and join have this)
* kubeadm: update reference docs includes for 1.14
- remove includes from alpha.md
- add upload-certs to init-phase.md
- add join-phase.md and it's phases
* kubeadm: update the editorial content of join and init
- cleanup master->control-plane node
- add some notes about phases and join
- remove table about pre-pulling images
- remove outdated info about self-hosting
* kubeadm: update target release for v1alpha3 removal
1.14 -> 1.15
* kubeadm: copy edits for 1.14 reference docs (part1)
* kubeadm: use "shell" for code blocks
* kubeadm: update the 1.14 HA guide (#13191)
* kubeadm: update the 1.14 HA guide
* kubeadm: try to fix note/caution indent in HA page
* kubeadm: fix missing sudo and minor amends in HA doc
* kubeadm: apply latest amends to the HA doc for 1.14
* fixed a few missed merge conflicts
* Admission Webhook new features doc (#12938)
- kubernetes/kubernetes#74998
- kubernetes/kubernetes#74477
- kubernetes/kubernetes#74562
* Clarifications and fixes in GMSA doc (#13226)
* Clarifications and fixes in GMSA doc
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Update configure-gmsa.md
* Reformat to align headings and pre-reqs better
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Reformat to align headings and pre-reqs better
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Reformat to fix bullets
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Reword application of sample gmsa
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Update configure-gmsa.md
* Address feedback to use active voice
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Address feedback to use active voice
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* RunAsGroup documentation for Progressing this to Beta (#12297)
* start serverside-apply documentation (#13077)
* start serverside-apply documentation
* add more concept info on server side apply
* Update api concepts
* Update api-concepts.md
* fix style issues
* Document CSI update (#12928)
* Document CSI update
* Finish CSI documentation
Also fix mistake with ExpandInUsePersistentVolumes documented as beta
* Overall docs for CSI Migration feature (#12935)
* Placeholder docs for CSI Migration feature
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Address CR comments and update feature gates
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Add mappings for CSI plugins
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Add sections for AWS and GCE PD migration
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Add docs for Cinder and CSI Migration info
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Clarify scope to volumes with file system
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Change the format of EBS and Cinder CSI Migration sections to follow the GCE template
Signed-off-by: Deep Debroy <ddebroy@docker.com>
* Windows documentation updates for 1.14 (#12929)
* Updated the note to indicate doc work for 1.14
* first attempt at md export from gdoc
* simplifyig
* big attempt
* moving DRAFT windows content to PR for review
* moving content to PR in markdown for review
* updated note tags
* Delete windows-contributing.md
deleting this file as it is already ported to the github contributor guide
* fixed formatting in intro and cluster setup guide
* updating formatting for running containers guide
* rejiggered end of troubleshooting
* fixed minor typos
* Clarified the windows binary download step
* Update _index.md
making updates based on feedback
* Update _index.md
updating ovn-kubernetes docs
* Update _index.md
* Update _index.md
* updating relative docs links
updating all the links to be relative links to /docs
* Update _index.md
* Update _index.md
updates for windows services and ovn-kubernetes
* formatted for correct step numbering
* fix typos
* Update _index.md
updates for flannel PR in troubleshooting
* Update _index.md
* Update _index.md
updating a few sections like roadmap, services, troubleshooting/filing tickets
* Update _index.md
* Update _index.md
* Update _index.md
* Fixed a few whitespace issues
* Update _index.md
* Update _index.md
* Update _index.md
* add section on upgrading CoreDNS (#12909)
* documentation for kubelet resource metrics endpoint (#12934)
* windows docs updates for 1.14 (#13279)
* Delete sample-l2bridge-wincni-config.json
this file is not used anywhere
* Update _index.md
* Update _index.md
* Update _index.md
* Update _index.md
* Update _index.md
* Rename content/en/docs/getting-started-guides/windows/_index.md to content/en/docs/setup/windows/_index.md
moving to new location
* Delete flannel-master-kubectl-get-ds.png
* Delete flannel-master-kubeclt-get-pods.png
* Delete windows-docker-error.png
* Add files via upload
* Rename _index.md to add-windows-nodes.md
* Create _index.md
* Update _index.md
* Update add-windows-nodes.md
* Update add-windows-nodes.md
* Create user-guide-windows-nodes.md
* Create user-guide-windows-containers.md
* Update and rename add-windows-nodes.md to intro-windows-nodes.md
* Update user-guide-windows-containers.md
* Rename intro-windows-nodes.md to intro-windows-in-kubernetes.md
* Update user-guide-windows-nodes.md
* Update user-guide-windows-containers.md
* Update user-guide-windows-containers.md
* Update user-guide-windows-nodes.md
* Update user-guide-windows-containers.md
* Update _index.md
* Update intro-windows-in-kubernetes.md
* Update intro-windows-in-kubernetes.md
fixing the pause image
* Update intro-windows-in-kubernetes.md
changing tables from html to MD
* Update user-guide-windows-nodes.md
converting tables from HTML to MD
* Update intro-windows-in-kubernetes.md
* Update user-guide-windows-nodes.md
* Update user-guide-windows-nodes.md
* Update user-guide-windows-nodes.md
updating the numbering , even though it messes up the notes a little bit. Jim will file a ticket to follow up
* Update user-guide-windows-nodes.md
* update to windows docs for 1.14 (#13322)
* Update intro-windows-in-kubernetes.md
* Update intro-windows-in-kubernetes.md
* Update intro-windows-in-kubernetes.md
* Update intro-windows-in-kubernetes.md
* Update intro-windows-in-kubernetes.md
* Update user-guide-windows-containers.md
* Update user-guide-windows-nodes.md
* Update intro-windows-in-kubernetes.md (#13344)
* server side apply followup (#13321)
* change some parts of serverside apply docs in response to comments
* fix typos and wording
* Update config.toml (#13365)
Existing details related to services are ambiguous as it does not give an idea when to use an environment variable for service discovery. Also, it does not talk about the DNS method of service discovery which is highly recommended. so corrected document to provide these missing details.
per the godocs:
// RootCAs defines the set of root certificate authorities
// that clients use when verifying server certificates.
// If RootCAs is nil, TLS uses the host's root CA set.
* E2E testing blog post
* E2E testing blog post: add information about optional command line flags
* Update and rename 2019-03-30-e2e-testing-for-everyone.md to 2019-03-22-e2e-testing-for-everyone.md
Adds a link to a new nodejs client library. New library builds on top of the godaddy lib, providing useful kubectl-like abstractions like `get` and `updateOrCreate`, and adds API-mapping and version-handling so the client code does not need to worry about compatibility across cluster versions.
The tutorial has somebody expose this service externally, so they should be getting NodePort or LoadBalancer not ClusterIP. I followed this tutorial and that's what I got (as expected)
* Create 2019-03-12-kubeedge-k8s-based-edge-intro.md
Initial created.
* Create kubeedge-highlevel-arch.png
* Adding KubeEdge High Level Arch img
Adding KubeEdge High Level Arch img for the blog
* Adding KubeEdge Logo img
Adding KubeEdge Logo img for blog
* Updated KubeEdge intro blog
Updated all the sections for KubeEdge, a k8s based edge computing platform.
(2019-03-12-kubeedge-k8s-based-edge-intro)
* Update 2019-03-12-kubeedge-k8s-based-edge-intro.md
Minor format updates
* Update 2019-03-12-kubeedge-k8s-based-edge-intro.md
* [ReviewFix] 2019-03-12-kubeedge-k8s-based-edge-intro.md
Review of @stewart-yu fixed for KubeEdge/kubeedge link
* [ReviewFix] Format 2019-03-12-kubeedge-k8s-based-edge-intro.md
Linefeed update.
* Update 2019-03-12-kubeedge-k8s-based-edge-intro.md
* Update 2019-03-12-kubeedge-k8s-based-edge-intro.md
* [ReviewFix] 2019-03-12-kubeedge-k8s-based-edge-intro.md
KubeEdge control plane in cloud and extension part made it mode clear.
* Update 2019-03-12-kubeedge-k8s-based-edge-intro.md
* Rename 2019-03-12-kubeedge-k8s-based-edge-intro.md to 2019-03-19-kubeedge-k8s-based-edge-intro.md
* Update 2019-03-19-kubeedge-k8s-based-edge-intro.md
* Create Kubernetes-setup-using-Ansible-and-Vagrant.md
This blog describes the steps for to setting up a multi node Kubernetes cluster using Ansible and Vagrant.
* Apply suggestions from code review
Co-Authored-By: ljnaresh <naresh_lj@infosys.com>
* Markdown changes for syntax highting and reviews.
* Vagrant image & join command logic changes
* Update Kubernetes-setup-using-Ansible-and-Vagrant.md
* Adding author name and organization
* Markdown correction for colon
* Update Kubernetes-setup-using-Ansible-and-Vagrant.md
At its current form minikube fails to start with following error:
unknown flag: --AllowedUnsafeSysctls
Renaming it to allowed-unsafe-sysctls works as expected.
* Update command outputs to k8s 1.13 based
* Update command outputs to k8s 1.13 based (2)
* Add the way to download the example manifest and change datetime in a pod log
* create a job from remote url
* Update content/en/docs/tasks/job/automated-tasks-with-cron-jobs.md
Co-Authored-By: makocchi-git <makocchi@gmail.com>
* Fix not available config field in kubeadm-init.md
Update the line describing `unifiedControlPlaneImage`, since "unifiedControlPlaneImage" in ClusterConfiguration was changed to a boolean field called "useHyperKubeImage" in v1beta1.
( https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta1 )
* Update image names and versions in kubeadm-init.md
$ kubeadm config images list
k8s.gcr.io/kube-apiserver:v1.13.4
k8s.gcr.io/kube-controller-manager:v1.13.4
k8s.gcr.io/kube-scheduler:v1.13.4
k8s.gcr.io/kube-proxy:v1.13.4
k8s.gcr.io/pause:3.1
k8s.gcr.io/etcd:3.2.24
k8s.gcr.io/coredns:1.2.6
# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
k8s.gcr.io/kube-proxy v1.13.4 fadcc5d2b066 10 days ago 80.3MB
k8s.gcr.io/kube-controller-manager v1.13.4 40a817357014 10 days ago 146MB
k8s.gcr.io/kube-scheduler v1.13.4 dd862b749309 10 days ago 79.6MB
k8s.gcr.io/kube-apiserver v1.13.4 fc3801f0fc54 10 days ago 181MB
k8s.gcr.io/coredns 1.2.6 f59dcacceff4 4 months ago 40MB
k8s.gcr.io/etcd 3.2.24 3cab8e1b9802 5 months ago 220MB
k8s.gcr.io/pause 3.1 da86e6ba6ca1 14 months ago 742kB
* Update the way to use custom etcd image in kubeadm-init.md
According to rosti's [comment](https://github.com/kubernetes/kubeadm/issues/1255#issuecomment-439874004),
the `image` field under `etcd` (from `v1alpha3`) was replaced by a couple of fields - `imageRepository` and `imageTag`.
* Apply suggestions from @neolit123 in kubeadm-init.md
Suggestions from @neolit123: https://github.com/kubernetes/website/pull/13068#pullrequestreview-212806230
* Apply a suggestion from @rosti in kubeadm-init.md
A suggestion from @rosti : https://github.com/kubernetes/website/pull/13068#discussion_r264228348
We've redone OpenUnison's k8s integration to provide multiple "spins". We created a new page to point users to the GitHub repo that matches the "spin" they're looking for.
In the calculation of this `Allocatable` will be `14.5 CPUs`, `28.5Gi` of memory and
`88Gi` of local storage. - It was 98Gi for storage instead of 88Gi which is derived after negating System-Reserved+Kube-reserved+eviction+hard
* Clarified step of getting Kubernetes cluster name; fixed quoting in command that sets `APISERVER`.
Need to set `CLUSTER_NAME` before using it.
The single quote in the `APISERVER` command prevented the expansion of the `CLUSTER_NAME` variable.
* Remove whitespace
* Fix SSH tunnel links
* Removed reference to GKE, which seemed to prompt the initial removal.
* Fixed the link to refer back to the correct paragraph now that it exists again.
* Noted deprecation of SSH tunnels but work to create a replacement.
Fix#8262
This reverts commit 1da65603af.
This reverts commit b8b71b6845.
* Update master-node-communication.md
Tidy up protocol support to show that TCP and UDP have support in
stable, whereas SCTP support is in alpha. For HTTP, direct users to
read up on Ingress instead.
* bluemix.net links are deprecated and no longer updated
* updated to new cloud.ibm.com link style
* also the product name is IBM Cloud Kubernetes Service, not Armada
* follow on to PR #12792
* Use feature-state note for CRI
* Note applicability to Linux hosts
* Explain cgroup ("control group")
* De-emphasize cgroup details
The individual runtime install steps already take account of this
advice.
* Fix bug about kubeadm upgrading
It will lead to the following error if using `yum upgrade -y kubeadm --disableexcludes=kubernetes` command:
<https://serverfault.com/questions/943696/fatal-unexpected-error-when-reading-kubeadm-config-configmap-clusterconfigurat>
Running `yum upgrade -y kubeadm --disableexcludes=kubernetes` command will upgrade the kubeadm to v1.13 but kubeadm v1.13 could not upgrade the v1.12 kubeadm cluster.
* Update kubeadm-upgrade-1-12.md
* Update kubeadm-upgrade-1-12.md
* Update kubeadm-upgrade-1-12.md
* add --csr-only option
The flag `--use-csr` is no longer available as of 1.13 on. Got replaced by `--csr-only`.
* replace deprecated kubeadm cert renewal flag
* Revising bluemix.net links to cloud.ibm.com
* bluemix.net links are deprecated and no longer updated
* updated to new cloud.ibm.com link style
* Removing blog content
* Create ingress-minikube.md
* Update ingress.md
* Move Ingress controllers content to own page
* Link to Set up Ingress on Minikube with the NGINX Controller task
* Minor edits
* Create ingress-controllers.md
* Update ingress-controllers.md
* 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.