* 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>
* Replaced "master" with newer terms in two places
- Replacing the outdated "master" term with API server.
- Changed "master" to "control plane node(s)"
* control plane node -> control plane
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
The rest of this paragraph talks about nodes being "machines," whereas this sentence is more specific, referring to virtual machines ("VMs"). The article this sentence points to also uses "machines" and isn't specific to VMs.
Original link says
```
Design proposals have been archived.
To view the last version of this document, see the Design Proposals Archive Repo.
Please remove after 2022-04-01 or the release of Kubernetes 1.24, whichever comes first.
```
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.
* Create updated dockershim FAQ
- The current dockershim FAQ is marked as outdated
- This new FAQ states clearly "removal"
- This new FAQ also has links to additional resources created by the community and others.
* deprecation -> removal scrub
- It's important this new FAQ says removal rather than deprecation as we're at that moment in time.
* Update content/en/blog/_posts/2022-02-16-updated-dockershim-faq.md
Did not know Hugo allowed for this.
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update content/en/blog/_posts/2022-02-16-updated-dockershim-faq.md
🤯
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update content/en/blog/_posts/2022-02-16-updated-dockershim-faq.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update content/en/blog/_posts/2022-02-16-updated-dockershim-faq.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update content/en/blog/_posts/2022-02-16-updated-dockershim-faq.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update content/en/blog/_posts/2022-02-16-updated-dockershim-faq.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Apply suggestions from code review
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Bump version to 1.23
Warning in 1.23
Removed in 1.24
* Update for today's date
Co-authored-by: Tim Bannister <tim@scalefactory.com>
The current example showing how to decode a secret
does it in several steps which is fine but if some level
of security is required will leak the encoded secret
value in the shell history thus making it retrievable.
This patch adds an example on how to retrieve that
value without exposing it.
Kubernetes Prow Robot