The current command on line 125 throws a permission error. The sudo elevation of rights applies to the containerd command, not the write (>) to a file owned by root.
This is the command as copied from the current page:
student@master:~$ sudo containerd config default > /etc/containerd/config.toml
-bash: /etc/containerd/config.toml: Permission denied
Instead leverage sudo tee. It works and no more error:
student@master:~$ containerd config default | sudo tee /etc/containerd/config.toml
fixing content in tabs on adding-windows-nodes.md
reworking tabbed content on adding-windows-nodes.md
intro-windows-in-kubernetes.md
Updating Windows pause image details
PR feedback for adding-windows-nodes.md
Updating comments got GMSA on containerD
After removing the sections of the page that are not in line with the
content guide, there is little left.
Edit pages that link to removed task to no longer link there.
Redirect using 302 status so that there is a future opportunity to reinstate
the page or something like it.
- Avoid links to removed cluster management task
- Broaden applicability of “Safely Drain A Node”
- Add (stub) cluster upgrade task page
- Add a basic page about upgrading your cluster.
- Add a task page about enabling or disabling HTTP APIs
Update the kubeadm upgrade documentation:
- Re-order the steps to drain / upgrade kubelet/kubectl / uncordon
- Remove the detailed output from apply and plan.
- Use {{ skew ... }} markers so that we can avoid more verbose changes
to the document.
- Apply minor / general cleanup (whitespace, missing ':')
* Adding cloud native security whitepaper blog post with image
* Injecting image in a markdown native way instead of html tags
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Switch image to SVG
* Update cloud native security whitepaper link
Linked to CNCF blog post
Co-authored-by: Tim Bannister <tim@scalefactory.com>
CKS is a two-hour, performance-based certification exam that provides
assurance that a certificant has the skills, knowledge, and competence on
a broad range of best practices for securing container-based applications
and Kubernetes platforms during build, deployment, and runtime. And now
it's live.