Hurtov Oleksii

> As a workaround, it was suggested to create the VPCGatewayAttachment via Cloudformation directly. @thodorisit Yeah, but in this case I need to detach the old VPCGateway, and this will...

UPD: I don't know why, but when I rebuilt the docker image locally from my laptop on the main branch and changed the image for the notification controller - it...

I have the same problems with cloud costs: 1. UI shows that integration is disabled. However in the logs I can find `Cloud Costs enabled: true`. I tested it on...

We are experiencing the same issue. We have such configMap: ``` apiVersion: "descheduler/v1alpha2" kind: "DeschedulerPolicy" profiles: - name: default-profile pluginConfig: - args: nodeAffinityType: - preferredDuringSchedulingIgnoredDuringExecution name: RemovePodsViolatingNodeAffinity plugins: deschedule: enabled:...

I found the issue. I needed to pass an additional parameter: evictLocalStoragePods. ``` profiles: - name: default pluginConfig: - args: evictLocalStoragePods: true name: DefaultEvictor ``` With this change, it started...

Hi! Just a heads-up - the Descheduler doesn’t actually schedule pods. It simply evicts them, and then the default Kubernetes scheduler takes over to decide where the pod should be...

@a7i > If you use `preferredDuringSchedulingIgnoredDuringExecution `, then I recommend enabling `nodeFit` check so that Descheduler only evicts them if there's another node available. > > > As a result,...

> If a pod has `preferredDuringSchedulingIgnoredDuringExecution`, CA is not going to force a scale-up as Scheduler will put it back on any available nodes (even if less desirable - which...

> It sounds to me that the CA `scale-down-unneeded-time`needs to be longer than your Descheduler interval. > > You can also increase the frequency of your descheduling cycle, but add...