* The link in access-cluster.md is stale
* service name segment of apiserver proxy must have trailing colon when
schema is specified
* Replace apiserver address with a reserved documentation IP address
Signed-off-by: Quan Tian <qtian@vmware.com>
This PR fixes the indentation nits in the
`port-forward-access-application-cluster` page.
We are not supposed to indent lines by 4 spaces because such
indentations may mislead the markdown parser to render them as code
snippets.
The acess-cluster-service page, has nothing to do with administering a cluster.
A better home for this page should be the `/docs/tasks/access-application-cluster` subdirectory instead.
* Fix broken anchor link of #type-nodeport in service.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in overview.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in ingress.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in troubleshooting-kubeadm.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in connecting-frontend-backend.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in source-ip.md
- general cleanup
- update sample output
- use more tooltips
- avoid specifying specific cloud providers
The website repo doesn't maintain a definitive list of cloud providers that
pass Kubernetes conformance tests. It's certainly more than AWS and GCP as
the previous revision stated.
k8s dashboard required https.
http does not currently have a corresponding endpoint.
So if you try to access it like this, you will get an error: "no endpoints available for service".
* Enhancements in clarity to docs/tasks/access-application-cluster/connecting-frontend-backend.md
* Code review comments
* Reverting name of service due to backed value in Dockerimage
Readers from several different backgrounds will find it useful to know
about how Kubernetes controls access to its API. Promote this overview
to the Security subsection of Concepts.
The commit (a79db9d5de) made the sample
YAML for Ingress a standalone file, but it was placed into a NEW
`examples/ingress` directory. This PR moves it to
`examples/service/networking` subdirectory where all other Ingress
examples are located. Having a single file under a dedicated directory
seems not good.
Clarify that `REMOTE_PORT` is interpreted as identifying a _Service_ port when provided `TYPE` is `service`.
Also, highlight support for specifying a named port as `REMOTE_PORT`.
There is a warning deprecation message for kubernetes v1.19:
```
Warning: networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
```
Switched apiversion in the example to `networking.k8s.io/v1`
* Revise Pod concept
Adapt the existing Pod documentation to suit the Docsy theme, by
promoting the Pod concept itself to /docs/concepts/workloads/pods/
Following on from this, update the Pod Lifecycle page to cover the
lifecycle of a Pod and follow on directly from the Pod concept,
for readers keen to understand things in detail.
This change also removes the automatic contents list from the Pod
overview page. Instead, the new page links to all the pages
inside the Pod section.
* Update links to Pod concept
Link to updated content
* Incorporate Pod concept suggestions
Co-authored-by: Celeste Horgan <celeste@cncf.io>
* Revise StatefulSet suggestion for Pod concept
Co-authored-by: Celeste Horgan <celeste@cncf.io>
Co-authored-by: Celeste Horgan <celeste@cncf.io>
Quite some resources have been moved out of the `extensions` API group
since 1.18; the `apps/v1beta1` and `apps/v1beta2` group versions are
also dropped. This PR updates the pages which still reference such API
groups or group versions.
Add description metadata for each task section (English localization).
For sections that only have one page, make sure that that sole page has
description metadata set.
This change helps prepare for the migration to the Docsy theme.
The previous content recommended running "kubectl version", which
will error out for readers who have not yet configured a cluster.
Reword with that in mind.
I fixed a Powershell command that you had provided in this document. Attempting to run the command with the format you supplied resulted in errors due to some conflict between using backwards slash for pathnames inside of parentheses.
The caution note was warning user about having Ingress Controller configured as prerequisite, but this is exactly what the tutorial is explaining.
Signed-off-by: Davi Garcia <dvercill@redhat.com>
Sean Wei
Kubernetes Prow Robot
Quan Tian
Qiming Teng
Thomas Güttler
Tim Bannister
Jordan Liggitt
Shu Muto
Alex McCarthy
Shivam Singhal
Mohit Sharma
Vaibhav
sandipanpanda
Guangwen Feng
ztzxt
Kartik Sharma
Michael McQuade
Rob Franken
Tyler Auerbeck
Hoon Jo
kahirokunn
Shubham Kuchhal
Grace Nguyen
kartik494
ms-choudhary
Ludovit Scholtz
Jihoon Seo
Derek Tamsen
Karen Bradshaw
Jailton Lopes
Leonardo Murillo
Cweiping
Charle Demers
Chuck Wilson
dharmendraImprowised
Qiming Teng
Christopher Montoro
Michael Nikitochkin
Dalibor Karlović
TAKAHASHI Shuuji
Andrew Allbright
divyabhushan
Celeste Horgan
Dave Barnow
viniciusbds
Gaurav Jain
Antonio Savage
Dmitry Tokarev
ntkjer
Daniel Barclay
Davi Garcia
Johnny Lim