Find portalIP automatically while updating a service

[hurf]

When I tried to update a service to change its port. Kubectl said spec.portalIp: invalid error ""

I viewed detailed information of the service and added portalIp with the same value as current service in the template and solved the problem.

But since the portalIp is automatically allocated when the service is created. Why users must provide portalIp explicitly while updating? And also the portalIp can not be changed while updating.

[bgrant0607]

Please see https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/api-conventions.md. PUT doesn't support partial updates. In general, you need to do a GET, change just what you want to update, and then PUT.

You could try PATCH, which was recently added. You may also be interested in a new merge strategy being implemented -- see #6027.

[bgrant0607]

And, yes, the description string on the field should say that the field "cannot be updated" -- @thockin.

[hurf]

@bgrant0607 - Thanks Brian, I'm not asking to allow portalIp be changed while updating, but allow users not giving portalIp explicitly in the template. I write a small patch to do so and will submit it soon.

[bgrant0607]

@hurf Thank you for offering to make a change, but the change will not be accepted. If you just want to update certain fields in the object, please use PATCH.

[bgrant0607]

I also recommend trying kubectl update --patch:
https://github.com/GoogleCloudPlatform/kubernetes/blob/bc4a082f7a5d1ec58a05c2f1a6fb1af9e5622079/docs/kubectl-update.md#L26

[thockin]

The description does say "cannot be updated".

[bgrant0607]

So it does.

[hurf]

@thockin @bgrant0607 - Sorry for the description mentioned "can not be updated" and not expressed myself clearly.

What I want to say is when I'm creating the pod, I didn't provide the portalIP in the template. But when I want to update the pod, I'm not going to change portalIP and it is not allowed to change it, why should I address it explicitly? I just feel inconvenient about this.

Anyway thanks you can discuss with this issue.

[bgrant0607]

@hurf I understand. The solution underway is #1702.