Swati Sehgal

Results 63 comments of Swati Sehgal

When I run kubectl get --raw "/apis/custom.metrics.k8s.io/v1beta1" | jq . I see the following metrics but am unable to access their values { "name": "jobs.batch/node_memory_MemTotal", "singularName": "", "namespaced": false, "kind":...

I referred to https://github.com/kubernetes-incubator/metrics-server/issues/90#issuecomment-412648296 in the issue https://github.com/kubernetes-incubator/metrics-server/issues/90 but wasn't able to access the metric values

> With #3574 merged this enhancement is `tracked` for the v1.26 release. Thank you! @marosset Looks like there is some mixup here. This enhancement is linked to https://github.com/kubernetes/enhancements/pull/3293 and not...

We had created https://github.com/kubernetes/kubernetes/pull/96275 to populate https://github.com/kubernetes/noderesourcetopology-api/ but at that time we had created this we were proposing changes in the default kube-scheduler and there were concerns around dependency of...

Apologies @Huang-Wei and @fromanirh, I should have done a better job at keeping you in the loop! Let's reopen https://github.com/kubernetes/kubernetes/pull/96275 and work on populating github.com/k8stopologyawareschedwg/noderesourcetopology-api then! Thanks for chiming in...

@dims We have concluded that we should go ahead and populate https://github.com/kubernetes/noderesourcetopology-api/. Is it okay to close this issue?

> /reopen > > [kubernetes/kubernetes#96275](https://github.com/kubernetes/kubernetes/pull/96275) was closed to inactivity and https://github.com/kubernetes/noderesourcetopology-api/ is still empty. Thanks Nikhita for reopening this issue. I didn't get a chance to update https://github.com/kubernetes/kubernetes/pull/96275 as I...

@nikhita Thank you so much for following-up on this. I wasn't able to work on this but certainly plan to do so. I will prioritize this work in the upcoming...

> Forgot to mention this in the meeting but can you look in to [moving](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) the repo instead? You can retain the issues, PRs, and releases instead of just moving...