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
|[ingress.kubernetes.io/ssl-redirect](#server-side-https-enforcement-through-redirect)|true or false|
@@ -213,6 +214,17 @@ This is possible thanks to the [ngx_stream_ssl_preread_module](https://nginx.org
213
214
214
215
By default NGINX uses `http` to reach the services. Adding the annotation `ingress.kubernetes.io/secure-backends: "true"` in the Ingress rule changes the protocol to `https`.
215
216
217
+
### Service Upstream
218
+
219
+
By default the NGINX ingress controller uses a list of all endpoints (Pod IP/port) in the NGINX upstream configuration. This annotation disables that behavior and instead uses a single upstream in NGINX, the service's Cluster IP and port. This can be desirable for things like zero-downtime deployments as it reduces the need to reload NGINX configuration when Pods come up and down. See issue [#257](https://github.com/kubernetes/ingress/issues/257).
220
+
221
+
222
+
#### Known Issues
223
+
224
+
If the `service-upstream` annotation is specified the following things should be taken into consideration:
225
+
226
+
* Sticky Sessions will not work as only round-robin load balancing is supported.
227
+
* The `proxy_next_upstream` directive will not have any effect meaning on error the request will not be dispatched to another upstream.
216
228
217
229
### Server-side HTTPS enforcement through redirect
0 commit comments