Mike Dame

@grcevski those are my favorite 2 options we've come across so far too. I think either one is justified for a project like this. The tooling option could also be...

The tricky part with go workspaces is it's really meant for local development (meaning it can be different for every developer based on their environment and folder structure), so it's...

With the custom sdk we're providing, do we still need the probes for the global instrumentation that we already have? Or could we just implement those functions in our sdk...

Didn't want to derail #1341 more, but also include `RemoveFailedPods` in the discussion here There is a lot of overlap between `RemoveFailedPods` and `PodLifetime` when you use the `states`/`reasons` and...

> should we let users set both included and excluded taints? When we look at namespace inclusion/exclusion we make inclusion be something like: "this and nothing else". Shouldn't we keep...

Hi @parkedwards, by default the managed Alertmanager doesn't do anything or interfere with self-deployed Alertmanagers. So simply by not configuring it, it is essentially "disabled". If you want to go...

x-ref https://github.com/kubernetes-sigs/descheduler/issues/225 /ok-to-test

Thanks @BenTheElder, that's a great suggestion and I think it's exactly what we've been looking for. It has always felt a bit weird that we were dependent on waiting until...

@a7i I'd say our master branch could always be building from source, with our tag branches using the released version The downside to that is we run the risk of...

It would block new PRs to the tagged branch until that image was available, so maybe the release branches could use the conditional switch like you're suggesting