break long lines
simplify wording (suggested by neolit123)
phrasing error/typo
don't mention creating a new kuebadm config file, not really relevant here
remove unnecessary stop from kubelet cert troubleshoot
minor phrasing improvement: *the* kublet
make the steps for fixing kubelet certs separate from other troubleshooting suggestions
move kubelet cert troubleshooting to a better place
improve note wording and add link
add missing dot
Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
add missing dot
Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
remove steps not related to the issue
Make instructions work on worker nodes too
Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
Hi There, When I follow these instructions, I could not install correctly kubectl. After kubectl file downloading, That file needs to be given execution permission.
I want to contribute for that. Best regards.
Improvement in Configure Service Accounts for Pods Task
Signed-off-by: Shubham Kuchhal <shubham.kuchhal@india.nec.com>
Remove annotations field from metadata.
Fix typo for the *volumeMount* field
Running the previous snippets with `kubectl apply -k .` would generate this error:
```
error validating ".": error validating data: ValidationError(Deployment.spec.template.spec.containers[0]): unknown field "volumeMount" in io.k8s.api.core.v1.Container;
```
According to [this page](https://kubernetes.io/docs/concepts/storage/volumes/), the correct field is "volumeMounts".
When reading these sentences, I thought that each pod must have the same values as each other pod. In other words, pod1's memory limit must equal pod2's memory limit.
It looks like I misunderstood; "must be the same" means that the limit and request values on each individual pod must match.
Clarify what "must be the same".
This removes the description of the ephemeral containers API from the
concepts section of the website. Most (all?) concepts don't have a
detailed description of their API in concepts. We added it for the
initial release of ephemeral containers because using the raw API was
the only way to add an ephemeral container.
This description of the API is no longer correct. Since it's now easy to
add an ephemeral container using `kubectl debug`, and this is too much
detail for a concepts section, we should remove the API description
entirely.
- Created glossary entries for manual and kubelet eviction
- Created node-pressure-eviction.md and api-eviction.md
- Merged content from eviction-policy.md and out-of-resource.md
- Added note to kube-scheduler about node conditions
- Deleted eviction-policy and out-of-resource.md
- Redirected old topics
- Change topic weights
hardikshah197