You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,8 +47,10 @@ service specified in the `autoneg` configuration annotation.
47
47
Only the NEGs created by the GKE NEG controller will be added or removed from your backend service. This mechanism should be safe to
48
48
use across multiple clusters.
49
49
50
-
Note: `autoneg`will initialize the `capacityScaler` variable to 1 on new registrations. On any changes, `autoneg` will leave
51
-
whatever is set in that value. The `capacityScaler` mechanism can be used orthogonally by interactive tooling to manage
50
+
By default, `autoneg` will initialize the `capacityScaler` to 1, which means that the new backend will receive a proportional volume
51
+
of traffic according to the maximum rate or connections per endpoint configuration. You can customize this default by supplying
52
+
the `initial_capacity` variable, which may be useful to steer traffic in blue/green deployment scenarios. On any changes, `autoneg`
53
+
will leave whatever is set in that value. The `capacityScaler` mechanism can be used orthogonally by interactive tooling to manage
52
54
traffic shifting in such uses cases as deployment or failover.
53
55
54
56
## Autoneg Configuration
@@ -67,6 +69,7 @@ Specify options to configure the backends representing the NEGs that will be ass
67
69
* `region`: optional. Used to specify that this is a regional backend service.
68
70
* `max_rate_per_endpoint`: required/optional. Integer representing the maximum rate a pod can handle. Pick either rate or connection.
69
71
* `max_connections_per_endpoint`: required/optional. Integer representing the maximum amount of connections a pod can handle. Pick either rate or connection.
72
+
* `initial_capacity`: optional. Integer configuring the initial capacityScaler, expressed as a percentage between 0 and 100. If set to 0, the backend service will not receive any traffic until an operator or other service adjusts the [capacity scaler setting](https://cloud.google.com/load-balancing/docs/backend-service#capacity_scaler).
returnfmt.Errorf("initial_capacity for backend %q must be between 0 and 100 inclusive, but was %q; see https://cloud.google.com/load-balancing/docs/backend-service#capacity_scaler for details", cfg.Name, *cfg.InitialCapacity)
0 commit comments