* Update hyperlinks to point to main branch
* Revert changes to post older than a year ⏪
* Update link to point to localize document 📝
* Fix fragement in the link 📝
change "#the-kubernetes-network-model" to "#how-to-implement-the-kubernetes-networking-model"
* Revert changes in zh localization pages
* Remove changes in files of other localization
* Adding an example
This text mentions that you can view the logs from a specific container by appending the container name. I've created an example, based on the previous few lines.
Also, I've added a -c flag, to bring this in line with both the ```kubectl logs``` [documentation's examples](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#logs) and other kubectl commands that require the -c flag when selecting a specific container from a pod.
* Wrapping long line and marking `-c` as code.
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
The `TracingConfiguration` struct we reference from the system traces
page only exists in the v1alpha1 version of the API server
configuration. This PR fixes the problem.
* Update logging.md
Updated some sentences for clarity.
* Update content/en/docs/concepts/cluster-administration/logging.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Primarily the change, in release 1.22, of how configuration objects
are maintained.
Also describe the new priority level.
Also move the sections on defaults and health check configuration to
follow the description of configuration objects.
This abandoned account was identified by a security researcher, and reported through the Kubernetes bug bounty program.
Don't we have a link checker that should identify cases like this? I'm guessing the github username was changed, so the link was redirecting (still valid), until the researcher recreated it. We should probably have the link checker flag redirects as well.
Removing this content seems to be appropriate:
Content does not contain a link to a CNI.
Content is not required for k8s to function.
Content seems to be replicated in longer form on the Google Cloud docs site.
Open vSwitch is in no way required for Kubernetes to function. Kubernetes is not mentioned once on this project's website, nor are there any instructions for how you might use this in a k8s environment.
This entry is not necessary for Kubernetes to function. Entry provides a link to the main corporate website, not to any relevant information. No CNI. Acronym refers to product marketing, not an actual technology.
Tim Allclair
Mark Andreev
Tim Bannister
Vedant Koditkar
Jay Beale
Qiming Teng
Tim Allclair
nwanati
Kubernetes Prow Robot
Michel Bongard
Mike Spreitzer
Shivam Singhal
ixodie
Shannon Kularathna
Neha Viswanathan
hhyasdf
Antonio Ojea
Jesse Butler
Bridget Kromhout
Patrick Ohly