![]() The fact that the .status.loadBalancer field can be set while .spec.type is not "LoadBalancer" is a flub. Any spec update will already clear .status.ingress, so it's hard to really rely on this. After this change, updates which try to set this combination will fail validation. Existing cases of this will not be broken. Any spec/metadata update will clear it (no error) and this is the only stanza of status. New gate "AllowServiceLBStatusOnNonLB" is off by default, but can be enabled if this change actually breaks someone, which seems exceeedingly unlikely. |
||
---|---|---|
.. | ||
apply_crd_beta_test.go | ||
apply_crd_test.go | ||
apply_test.go | ||
main_test.go | ||
reset_fields_test.go | ||
scale_test.go | ||
status_test.go |