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: docs/guide/ingress/annotations.md
+19-9Lines changed: 19 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -285,18 +285,19 @@ Traffic Routing can be controlled with following annotations:
285
285
286
286
The `action-name` in the annotation must match the serviceName in the Ingress rules, and servicePort must be `use-annotation`.
287
287
288
-
!!!note "use ARN in forward Action"
289
-
ARN can be used in forward action(both simplified schema and advanced schema), it must be an targetGroup created outside of k8s, typically an targetGroup for legacy application.
288
+
!!!note "use TargetGroupARN/TargetGroupName in forward Action"
289
+
TargetGroupARN/TargetGroupName can be used in forward action(both simplified schema and advanced schema), it must be a target group created outside of k8s, typically a targetGroup for a legacy application.
290
290
!!!note "use ServiceName/ServicePort in forward Action"
291
-
ServiceName/ServicePort can be used in forward action(advanced schema only).
291
+
ServiceName/ServicePort can be used in forward action(advanced schema only).
292
292
293
293
!!!warning ""
294
-
[Auth related annotations](#authentication) on Service object will only be respected if a single TargetGroup in is used.
294
+
[Auth related annotations](#authentication) on a Service object will only be respected if a single TargetGroup is used.
295
295
296
296
!!!example
297
297
- response-503: return fixed 503 response
298
298
- redirect-to-eks: redirect to an external url
299
299
- forward-single-tg: forward to a single targetGroup [**simplified schema**]
300
+
- forward-single-tg-by-name: forward to a single targetGroup identified by its name [**simplified schema**]
300
301
- forward-multiple-tg: forward to multiple targetGroups with different weights and stickiness config [**advanced schema**]
301
302
302
303
```yaml
@@ -313,8 +314,10 @@ Traffic Routing can be controlled with following annotations:
@@ -342,6 +345,13 @@ Traffic Routing can be controlled with following annotations:
342
345
port:
343
346
name: use-annotation
344
347
- path: /path2
348
+
pathType: Exact
349
+
backend:
350
+
service:
351
+
name: forward-single-tg-by-name
352
+
port:
353
+
name: use-annotation
354
+
- path: /path3
345
355
pathType: Exact
346
356
backend:
347
357
service:
@@ -647,7 +657,7 @@ ALB supports authentication with Cognito or OIDC. See [Authenticate Users Using
647
657
- <aname="auth-idp-oidc">`alb.ingress.kubernetes.io/auth-idp-oidc`</a> specifies the oidc idp configuration.
648
658
649
659
!!!tip ""
650
-
You need to create an[secret](https://kubernetes.io/docs/concepts/configuration/secret/) within the same namespace as Ingress to hold your OIDC clientID and clientSecret. The format of secret is as below:
660
+
You need to create a[secret](https://kubernetes.io/docs/concepts/configuration/secret/) within the same namespace as Ingress to hold your OIDC clientID and clientSecret. The format of secret is as below:
651
661
```yaml
652
662
apiVersion: v1
653
663
kind: Secret
@@ -667,7 +677,7 @@ ALB supports authentication with Cognito or OIDC. See [Authenticate Users Using
667
677
- <aname="auth-on-unauthenticated-request">`alb.ingress.kubernetes.io/auth-on-unauthenticated-request`</a> specifies the behavior if the user is not authenticated.
668
678
669
679
!!!info "options:"
670
-
* **authenticate**: try authenticate with configured IDP.
680
+
* **authenticate**: try to authenticate with configured IDP.
671
681
* **deny**: return an HTTP 401 Unauthorized error.
672
682
* **allow**: allow the request to be forwarded to the target.
673
683
@@ -837,10 +847,10 @@ TLS support can be controlled with the following annotations:
837
847
- This annotation is not applicable for Outposts, Local Zones or Wavelength zones.
838
848
- "Configuration Options"
839
849
- `port: listen port `
840
-
- Must be a HTTPS port specified by [listen-ports](#listen-ports).
850
+
- Must be an HTTPS port specified by [listen-ports](#listen-ports).
- `verify` mode requires an existing trust store resource.
843
-
- See [Create a trust store](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/mutual-authentication.html#create-trust-store) in the AWS documentation for more details.
853
+
- See [Create a trust store](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/mutual-authentication.html#create-trust-store) in the AWS documentation for more details.
844
854
- `trustStore: ARN (arn:aws:elasticloadbalancing:trustStoreArn) | Name (my-trust-store)`
845
855
- Both ARN and Name of trustStore are supported values.
0 commit comments