* csi-ephemeral-inline-volumes: introduce CSI support for ephemeral inline volumes
This was alpha in Kubernetes 1.15 and became beta in 1.16. Several CSI
drivers already support it (soon...).
* csi-ephemeral-inline-volumes: bump date and address feedback (NodeUnpublishVolume)
* csi-ephemeral-inline-volumes: add examples and next steps
* csi-ephemeral-inline-volumes: rename file, minor edits
* csi-ephemeral-inline-volumes: include Docker example
Tiny fix
Feedback from onlydole
Add missing link
Incremental fixes
Revise Jim's job title
Update content/en/blog/_posts/2020-01-17-Docs-Review-2019.md
Co-Authored-By: Celeste Horgan <celeste@cncf.io>
Feedback from celeste, change date
* Fixed outdated ECR credential debug message
The log message for troubleshooting kubelet auto fetching ECR credentils issue has been changed (noticed since 1.14), and the new message reads like this when verbose log level is set to 3:
- `aws_credentials.go:109] unable to get ECR credentials from cache, checking ECR API`
- `aws_credentials.go:116] Got ECR credentials from ECR API for <Your ECR AWS Account ID>.dkr.ecr.us-east-1.amazonaws.com`
This is based on the kubelet source code:
https://github.com/kubernetes/kubernetes/blob/release-1.14/pkg/credentialprovider/aws/aws_credentials.go#L91
This PR is to fix this and to avoid confusion for more people who are troubleshooting the kubelet ECR issue.
* Update content/en/docs/concepts/containers/images.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
On the page, it says `as you .KUBECONFIG` whereas it is meant `as your
.KUBECONFIG`. Minor annoyance, but still benefits fixing. One char PR.
Signed-off-by: Mariyan Dimitrov <mariyan.dimitrov@gmail.com>
* Added a new section on Azure CNI
Azure provides a CNI for native integration of Kubernetes Pods in a Virtual Network. I have added a short description of this CNI and provided links to important documentation
* Update networking.md
* Made updates based on comments
This is much closer to what you are recommending. Please take a look
The kubeadm survey for 1.13:
https://docs.google.com/forms/d/1A855D054FZfdvNbx6mAa54tcZ204GmPCIhxe1UrXKd8/edit#responses
The kubeadm survey for 1.13:
https://docs.google.com/forms/d/1A855D054FZfdvNbx6mAa54tcZ204GmPCIhxe1UrXKd8/edit#responses
Revealed the top 3 plugins in terms of popularity are:
Flannel
Calico
WeaveNet
The kubeadm maintainers are in contact with the maintainers
of these plugins and can provide support and updates to this guide.
The rest of the plugins in the guide are unmaintained, by the kubeadm team!
Some plugins are not in the CNCF landscape, or maintained by the kubeadm team, but still
present in the guide.
Remove the following non-CNCF / unmaintained plugins:
AWS VPC
Romana
Juniper*
Canal (it is an alternative to Calico and already explained in the
Calico guide)
Add note that users can still defer to this page for more options and a more complete list:
https://kubernetes.io/docs/concepts/cluster-administration/networking/Revealed the top 3 plugins in terms of popularity are:
- Flannel
- Calico
- WeaveNet
The kubeadm maintainers are in contact with the maintainers
of these plugins and can provide support and updates to this guide.
Some plugins are not in the CNCF landscape, but still
covered in this page:
https://kubernetes.io/docs/concepts/cluster-administration/networking/
Remove the following non-CNCF plugins:
- AWS VPC
- Romana
- Juniper*
- Canal (it is an alternative to Calico and already explained in the
Calico guide)
Add note that users can still defer to this page for more options:
https://kubernetes.io/docs/concepts/cluster-administration/networking/
* Use Control Plane instead of Master
* improve image. The SVG was not matching the PNG, so I basically had to re-create it from scratch. I kept the visual similarities as mush as possible
* remove tautological phrase
* fix glossary references as well
* improve cluster glossary to move from Master to Control Plane
* improve english form
* Fix pod status phases + more
A number of improvements introduced in the glossary entry for Pod Lifecycle
* Completed / CrashLoopBackOff were removed from the list of pod status phases
* The link to PodStatus in the generated kubernetes api was parametrized regarding version
* Minor editorial changes
* Rework Pod Lifecycle entry to better describe term
The term definition was reworked after the review comments from
kbhawkey
* Looping over logs of all jobs using a single command
Using the label constuct `-l` to loop over output of all jobs (or pods) using a single command
* Update content/en/docs/tasks/job/parallel-processing-expansion.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Add descriptions of CPU and Memory metrics
* Update content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* address comments
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update kubernetes-api.md
Updated the docs to reflect a change that has already been made in v1.14 instead of going to be made in v1.14 with us being at v1.16 now.
* Update content/en/docs/concepts/overview/kubernetes-api.md
Co-Authored-By: Barnabas Makonda <6409210+makoscafee@users.noreply.github.com>
Co-authored-by: Barnabas Makonda <6409210+makoscafee@users.noreply.github.com>
* Update scheduling-hugepages.md
Correcting the yaml file contents, verified the pod deployment
* Update content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
DNS debugging documentation is using a busybox image as example.
This image has different known issues with the way it resolves
the DNS names in k8s, creating confusion with users that try to
follow the docs.
The e2e tests use a custom small image ~4.3MB for DNS testing
with all the necessary tools. Also, the fact that this image is
being used for the k8s e2e testing guarantees it's compatibility.
* Add tooltip for addons in Hello Minikube page
* Update glossary title and add more descriptive info
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Extend Cilium CNI plugin description
Mention that it works on top of other CNI plugins due to the CNI
chaining [1].
[1]: http://docs.cilium.io/en/v1.6/gettingstarted/cni-chaining/
Signed-off-by: Martynas Pumputis <m@lambda.lt>
* Update Cilium installation steps for kubeadm
- Use the latest v1.6 Cilium.
- By default, Cilium no longer needs/deploys ETCD store.
Signed-off-by: Martynas Pumputis <m@lambda.lt>
* Update Cilium NetworkPolicy guide
- Update minikube min version requirement.
- Use Cilium v1.6.
- Remove the etcd store bits, as Cilium v1.6 no longer depend on
it by default.
Signed-off-by: Martynas Pumputis <m@lambda.lt>
* Update Cilium installation steps for kubeadm
- How to run without kube-proxy.
Signed-off-by: Martynas Pumputis <m@lambda.lt>
Co-authored-by: Martynas Pumputis <m@lambda.lt>
* Exchanged developers with containers
The meaning of original sentence: "Coordinating ports across multiple **developers** is very difficult to do at scale..." is not really obvious. From what I understand from the context of this page, the term **containers** would make more sense, because the context in this paragraph is on containers and ports rather than developers.
* Clarify terms developer and container
Rephrased statement on port coordination to make
it claerer that the ports are part of the
containers provided by developers or teams.
* Update content/en/docs/concepts/services-networking/connect-applications-service.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
changes for #14526 had either a stray "for a" or missed "service" as in "for a service".
Since it's quite lengthy and "for a service" is unnecessary in service.md, I opted to removed it.
* Specify minimum Kubernetes version for Job tasks
Ask for v1.8 because CronJob went beta in v1.8 and some of the Job pages
reference CronJob.
* Drop version check from Job / CronJob task pages.
Assume that readers have Kubernetes v1.8 or newer.
* Added Azure Application Gateway Ingress Controller
Added Azure AppGW Ingress Controller (AGIC) to the list of additional controllers now that it has gone GA.
* Update content/en/docs/concepts/services-networking/ingress-controllers.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Improve CronJob page
This PR adds a note about the special constraint on CronJob names. The
contstraint is not captured in the API specification or anywhere else to
my knownledge.
* Update content/en/docs/concepts/workloads/controllers/cron-jobs.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
I noticed this https://www.base64encode.org/ Tool is not working in the safari browser, So I added alternative tool that I found is working on safari and another browser.
Please Check Link that I added :)
Thanks
I searched for obvious replacements using Google, but did not see any.
(I don't want to hyperlink to blog posts, as blogs don't come with any
commitment for someone to keep them current).
The earlier E2E blog post touch on some of these aspects, but was more
focused on writing a custom test suite. Using the existing tests
unchanged may be simpler and sufficient. Because it is not that
well-known yet, a blog post seems useful.
- move the sections about custom certificates and external CA
to the kubeadm-certs page
- minor cleanups to the kubeadm-certs page, including updated output
for the check-expiration command
- link the implementation details page to the new locations
for custom certs and external CA
* Update cluster health check command for newer etcd
Existing docs assume the older (v3.2) etcdctl `health-check` command but with a 3.4.3 cluster (which is what kubeadm creates in the static manifest now), that subcommand is no longer supported and returns 404 errors like:
```
root@etcd-1:~# docker run --rm -it --net host -v /etc/kubernetes:/etc/kubernetes quay.io/coreos/etcd:${ETCD_TAG} etcdctl --cert-file /etc/kubernetes/pki/etcd/peer.crt --key-file /etc/kubernetes/pki/etcd/peer.key --ca-file /etc/kubernetes/pki/etcd/ca.crt --endpoints https://10.170.68.181:2379 cluster-health
cluster may be unhealthy: failed to list members
Error: unexpected status code 404
```
* PR review changes
* Adding helm3 command
helm3 doesn't have name flag hence above command fails when user is using helm3(which is latest in its kind)
* adding tab for Helm3 and defaulting it
* addressing comments
In 203391835d, an explicit anchor '#noderestriction' was added to the
NodeRestriction section of the Admission Controllers reference document,
which caused the link to the '#NodeRestriction' anchor in the Node
Authorization document to break and lead to the top of the Admission
Controllers document instead of to the NodeRestriction section further
down the page. This change fixes the link to point to the intended
section instead of to the whole page in general.
* Blog post links (hugo issue)
This commit aims to fix multiple occurrences of issue introduced before
switching blog engine to hugo, after which no blog links with "." was
working.
It's include a huge ammount of links with kubernetes version in it.
This commit also include one or two additional link fixes found while
making changes in attempt to solve current situation.
* Additional fix for Chinese website blog post.
* Clarify port selection section
Avoids situation where a beginner is directed to enter the wrong port and has to backtrack and reread.
* Update content/en/docs/tutorials/hello-minikube.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Update documentation to reflect Go 1.13 dependency for Kubernetes 1.17+
* Rephrased required Golang version
* Updated french translation to match English Golang version
Without this change, the instruction to "get familiar with" the Pods
concept directs the user to the pods section of the User Guide, which
actually redirects to the "Run a Stateless Application Using a
Deployment" task, which is not strictly about Pods. This change fixes
the link to point to the Pods Overview in the Concepts section, which
makes more sense in this context.
Sharjeel Aziz
Naoki Oketani
makocchi
Joe Betz
Shivang Goswami
Kaitlyn Barnard
Eugenio Marzo
Patrick Ohly
Shunde Zhang
Zach Corleissen
Steve Bang
lemon
Xin Chen
0xC45
YAMAMOTO Takashi
Mariyan Dimitrov
Gerasimos Dimitriadis
Shivesh Abhishek
Aanand Ramachandran
Marc Bihlmaier
wawa
Lubomir I. Ivanov
Alexander Zhukov
Rodrigo Queiro
Ajay Kemparaj
Kartik494
Ismail Alidzhikov
Sascha Grunert
RA489
Fabio Alessandro Locati
mvgijssel
camper42
tom1299
Maya Kaczorowski
Jan-Philip Gehrcke
Jacky Wu
Anoop Kumar
David Ashpole
Deepankar Malhan
kvaps
mantri425
Erik Stidham
Antonio Ojea
David M. Lentz
Qiming Teng
Samuel Kihahu
Tim Bannister
ares
Arjun
Rob Scott
Paco Xu
Taylor Dolezal
Dominic Yin
Habib Ridho
shubham
craigbox
Raj Babu Das
Pablo Castellano
André Martins
zhouya0
ThoTischner
Manuel Rüger
Jonathan McCall
vyask
Slava Semushin
Jan Wozniak
Wojciech Sciesinski
Eric Covener
Javier Revillas
chendotjs
Anshu Prateek
Jesang Myung
huccshen
Poule Dodue
Cat Yao
giri
windayski
GoodGameZoo
David Zhu
jkld11
KYamani
Jin Hase
Claudia J.Kang
Paul Morie
Aðalsteinn Rúnarsson
Rahul Kumar Singh
helight
Antoine Pelisse
Mikalai Radchuk
melvinrmc
bob wang
Eric Smalling
Ivan Boyko
Karen Bradshaw
Prashant Arya
Oleg Butuzov
Colleen Murphy
xieyanker
pierwill
Cria Hu
Takahiro Tsuruda
Xiang Dai
Chen, Xu Chun (Simon)
RobertKalnins
yuxiaobo96
Thomas
chendotjs
Sascha Grunert
vishakha