Release v0.8.0 · armadaproject/armada

Breaking Changes

#3660 can potentially cause big changes to the maximum proportion of the farm that queues are allowed to use. Before, if you partially overrode limits at a more fine-grained level, limits not overridden would default to unlimited. Now they will default to the level above. For example, previously, if you overrode only cpu at the queue+priority class level, memory would be unlimited. Now memory will fall back to the priority class cap.

Fix flakey tests in getjobs_test + improve JobRuntime tests by @JamesMurkin in #3654
Change default node-type from pool name to none by @JamesMurkin in #3648
Adding query API endpoints to python client by @MustafaI in #3650
Update K8s dependency to 1.26.x by @d80tb7 in #3643
Single Postgres Configuration In API by @d80tb7 in #3656
Set scheduling termination reason when scheduling constraint hit by @JamesMurkin in #3655
Remove unused config + related code by @JamesMurkin in #3653
Remove queue ttl by @d80tb7 in #3649
remove pgtype dependency by @d80tb7 in #3652
Remove Eviction Probability Config Values by @d80tb7 in #3651
Scheduler: fall back correctly when per-queue resource limits are partially specified by @robertdavidsmith in #3660

Full Changelog: v0.7.1...v0.8.0