-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Resource Topology Exporter with podresource API
Kubelet exposes endpoint at `/var/lib/kubelet/pod-resources/kubelet.sock` for exposing information about assignment of devices to containers. It obtains this information from the internal state of the kubelet's Device Manager and returns a single PodResourcesResponse enabling monitor applications to poll for resources allocated to pods and containers on the node. This makes PodResource API a reasonable way of obtaining allocated resource information. However, PodResource API:https://godoc.org/k8s.io/kubernetes/pkg/kubelet/apis/podresources/v1alpha1 currently only exposes devices as the container resources (without topology info) and hence we are proposing KEP:kubernetes/enhancements#1884 to enhance it to expose CPU information along with device topology info. In order to use pod-resource-api source in Resource Topology Exporter, we need to use this:https://github.com/kubernetes/kubernetes/pull/93243/files patched version of kubelet implementing chnages proposed in the aforementioned KEP. This will no longer be needed once the KEP and the PR are merged. - Added command line argument to specify source, enabling user to specify either cri or pod-resource-api - Created PodResourceFinder struct and supporting methods to enable support for pod-resource-api as a way of gathering information of allocated resources - Created NodeResources struct to be used for storing node resource information - Moved functions (updateNUMAMap(), Aggregate() and makePCI2ResourceMap()) used by both crifinder.go and podresourcefinder.go to finder.go - Narrowed down volume mounts to the required subtree - Updated README Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
- Loading branch information
1 parent
7055146
commit ed82210
Showing
9 changed files
with
828 additions
and
408 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.