Based on the discussion here: https://github.com/kubernetes/kubernetes/pull/97415#discussion_r722548437
we explictly state that the GetCpuIds returned for a ContainerResource in the ListPodResourcesResponse
represent only exclusively allocated CPUs.
In order to evaluate the CPUs corresponding to the shared pool, List endpoint should be used in conjunction
with GetAllocatableResources endpoint. We highlight the steps that the client needs to take evaluate this.
Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
Also, explicitly clarify the behavior of GetAllocatableResources
The explanation that GetAllocatableResources can be used to obtain available resources
on the node can be misinterpretted as an API that is used to obtain free/unallocated
resources on a node.
This PR adds additional text to clarify that this API endpoint only returns
allocatable resources which are resources exposed to kubelet as defined here:
https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable.
Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
* Fixes grammatical errors
* Removes period as recommended in review
* Update content/en/docs/setup/production-environment/tools/kubespray.md
Co-authored-by: Rey Lejano <rlejano@gmail.com>
Co-authored-by: Rey Lejano <rlejano@gmail.com>
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.
Add missing note to review Kubernetes Network Policy Ingress rules during debugging Kubernetes Service issues
Update document link
Co-authored-by: Qiming Teng <tengqm@outlook.com>
The 'kubr' gem has last been updated 7 years ago. It doesn't provide the required modern functionalities. The documentation consists of one code example and that's it. It's inclusion in this list only wastes time of Ruby on Rails developers because no sane person would chose it.
* 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
This change updates the information about the node controller in the
cloud controller managers. The node controller is not responsible for
creating new node objects, it updates them with information from the
provider infrastructure.
* kubelet-in-userns.md: fix typoes
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
* kubelet-in-userns.md: fix unexpected config paths
Referring to `/etc/containerd/config.toml` makes sense only when the user has
read/write permissions to `/etc/containerd/config.toml` in the current mount
namespace, which is not always assumed in the context of this documentation.
The same applies to `/etc/crio/crio.conf`, too.
Partially revert PR 30020.
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
* kubelet-in-userns.md: add back the link to example port forwarder implementation
Add back the link to `k3s/pkg/rootlessports/controller.go` removed in PR 30020.
As stated in `{{ <note> }}`, the corresponding section is written for developers
of Kubernetes distros, not for end users.
So we should retain the implementation details here.
Partially revert PR 30020.
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>