Restore deprecatedPublicIPs for compat

The v1 API will retain deprecatedPublicIPs, but externalIPs is preferred.
This commit is contained in:
Tim Hockin
2015-09-23 17:46:18 -07:00
parent fd91d3f0ec
commit f14709b493
6 changed files with 67 additions and 20 deletions

View File

@@ -13818,7 +13818,14 @@
"items": {
"type": "string"
},
"description": "ExternalIPs are used by external load balancers, or can be set by users to handle external traffic that arrives at a node. Externally visible IPs (e.g. load balancers) that should be proxied to this service."
"description": "externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. The user is responsible for ensuring that traffic arrives at a node with this IP. A common example is external load-balancers that are not part of the Kubernetes system. A previous form of this functionality exists as the deprecatedPublicIPs field. When using this field, callers should also clear the deprecatedPublicIPs field."
},
"deprecatedPublicIPs": {
"type": "array",
"items": {
"type": "string"
},
"description": "deprecatedPublicIPs is deprecated and replaced by the externalIPs field with almost the exact same semantics. This field is retained in the v1 API for compatibility until at least 8/20/2016. It will be removed from any new API revisions. If both deprecatedPublicIPs *and* externalIPs are set, deprecatedPublicIPs is used."
},
"sessionAffinity": {
"type": "string",