Tim Hockin 80dda49ce2 Service: Fix semantics for Update wrt allocations ... It is not uncommon for users to Create a Service and not specify things like ClusterIP and NodePort, which we then allocate for them. They same that YAML somewhere and later use it again in an Update, but then it fails. That's because we detected them trying to set a ClusterIP from a value to "", which is not allowed. If it was just NodePort, they would actually succeed and reallocate a new port. After this change, we try to "patch" updates where the user did not specify those values from the old object.		2021-07-07 17:09:12 -07:00
..
make.go	Service: Fix semantics for Update wrt allocations	2021-07-07 17:09:12 -07:00