On the Service object side, the method is to set loadBalancerIP in the spec. The implementing side for Services has to then do the appropriate operations to ei

On the Service object side, the method is to set loadBalancerIP in the spec. The implementing side for Services has to then do the appropriate operations to either get you that IP, or fail creation of Service. On GCP, if you set loadBalancerIP to IP of a persistent, unattached public IP you own, it will automatically attach to it. I expect similar behaviour on AWS and others.