feat: kube-scheduler local dev #1116
Merged
+120
−36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds kube-scheduler metrics to the local dev environment.
It was necessary to switch from
k3d
tokind
to access the newkube_pod_resource_request
andkube_pod_resource_limit
. It also appears that a new job is required to scrape these metrics, as they're exported on a separate endpoint (/metrics/resources
). This could have implications for #815 (cc @rexagod).Here's a screenshot showing the scheduler dashboard and the usual
kube-scheduler
job:To test this out for yourself, checkout this branch and run: