Mike Dame
Mike Dame
This is a problem that unfortunately affects metrics collection for any short-lived workload (I was working on the same issue for serverless recently). So, it's not just a descheduler issue...
#1187 seems pretty open ended, looks like there is some architectural changes in the first comment. But other things like nodeFit updates or other features can be added later. Could...
@knelasevero that issue lists a lot of tasks, and it's not clear which are done or in progress, or the priority that they need to be done in. So, that's...
@knelasevero sounds good, sorry to derail this PR. I'm +1 to unblocking it then. By "break off" I meant make it clear where our support/feature set for v1alpha1 is ending...
Hi, this is working as intended. The descheduler does not know about cluster-level default constraints because it does not have access to the cluster's KubeSchedulerConfiguration.
/remove-kind bug /kind feature
Yes, exactly. This has been discussed before if you'd like some more info: https://github.com/kubernetes-sigs/descheduler/issues/609 Essentially the KubeSchedulerConfiguration isn't an actual API object, it's just mounted to the scheduler pod. Users...
> Overall seems fine to me, although I'd advocate for us to migrate over to our Hugo + Netlify setup as a fast follow. Yeah, this should get a good...
@svrnm based on Austin's comment above, it sounds like creating a GCP project shouldn't take much time. The rest of the steps I've outlined let us drop-in the existing solution...