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>
In my humble view, `kubectl certificate approve my-svc.my-namespace` command may understand easily to follow up this procedure.
Update managing-tls-in-a-cluster.md
Change some text as Divya Mohan's guidance.
Update managing-tls-in-a-cluster.md
Change text as sftim's guidance.! Thank you so much!
* 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>
Introduce concepts in an order that should suit people new to
Kubernetes, so that you don't encounter details like volume cloning
until you've seen more of the basic volume types (persistent,
ephemeral, projected).
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>
Kubernetes Prow Robot