Tim Hockin e927ce85b6 service REST: Call Decorator(old) on update path ... This is causing a bug when upgrading from older releases to 1.23 because of Service's maybe-too-clever default-on-read logic. Service depends on `Decorator()` to be called upon read, to back-populate old saved objects which do not have `.clusterIPs[]` set. This works on read, but the cache saves the pre-decorated type (as it is documented) In 1.23, this code was refactored and it seems some edge-case handling was inadvertently removed (I have not confirmed exactly what happened). Test by aojea		2022-01-30 11:25:17 -08:00
..
loadbalancer_test.go	Mark ServiceLBNodePortControl as GA	2021-12-16 16:48:58 +01:00
main_test.go
service_test.go	add integration test validating that converting a Service to ExternalName results in the field being dropped on read	2022-01-05 12:41:53 -05:00
upgrade_test.go	service REST: Call Decorator(old) on update path	2022-01-30 11:25:17 -08:00