7 Commits

Author	SHA1	Message	Date
Patrick Ohly	2472291790	api: introduce separate VolumeResourceRequirements struct ... PVC and containers shared the same ResourceRequirements struct to define their API. When resource claims were added, that struct got extended, which accidentally also changed the PVC API. To avoid such a mistake from happening again, PVC now uses its own VolumeResourceRequirements struct. The `Claims` field gets removed because risk of breaking someone is low: theoretically, YAML files which have a claims field for volumes now get rejected when validating against the OpenAPI. Such files have never made sense and should be fixed. Code that uses the struct definitions needs to be updated.	2023-08-21 15:31:28 +02:00
Kante Yin	2d866ec2fc	Teardown only scheduler in integration tests ... Signed-off-by: Kante Yin <kerthcet@gmail.com>	2023-05-04 10:09:24 +08:00
Wojciech Tyczyński	8a959396b8	Clean shutdown of volumescheduling integration tests	2022-05-28 21:14:09 +02:00
kerthcet	835cdd6d81	fix: resolve goroutine leak in volumescheduling integration tests ... Signed-off-by: kerthcet <kerthcet@gmail.com>	2022-05-06 17:51:17 +08:00
Mike Dame	4960d0976a	Wire contexts to Core controllers	2021-11-01 10:29:00 -04:00
Mengjiao Liu	da35add03f	Rename master to apiserver in test/integration	2021-06-17 15:48:39 +08:00
Yecheng Fu	8f3782226f	Prioritizing nodes based on volume capacity: integration tests	2021-03-05 23:59:25 +08:00