-
Notifications
You must be signed in to change notification settings - Fork 690
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Steve Kriss <krisss@vmware.com>
- Loading branch information
Showing
1 changed file
with
8 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
## Gateway provisioner: support requesting a specific address | ||
|
||
The Gateway provisioner now supports requesting a specific Gateway address, via the Gateway's `spec.addresses` field. | ||
Only one address is supported, and it must be either an `IPAddress` or `Hostname` type. | ||
The value of this address will be used to set the provisioned Envoy service's `spec.loadBalancerIP` field. | ||
If for any reason, the requested address is not assigned to the Gateway, the Gateway will have a condition of "Ready: false" with a reason of `AddressesNotAssigned`. | ||
|
||
If no address is requested, no value will be specified in the provisioned Envoy service's `spec.loadBalancerIP` field, and an address will be assigned by the load balancer provider. |