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
Traffic Routing can be controlled with following annotations:
43
47
48
+
- <aname="lb-type">`service.beta.kubernetes.io/aws-load-balancer-type`</a> specifies the load balancer type. This controller reconciles those service resources with this annotation set to either `nlb-ip` or `external`.
49
+
50
+
!!!note ""
51
+
- For `nlb-ip` type, controller will provision NLB with IP targets. This value is supported for backwards compatibility
52
+
- For `external` type, NLB target type depend on the annotation [nlb-target-type](#nlb-target-type)
53
+
54
+
!!!warning "limitations"
55
+
- This annotation should not be modified after service creation.
- <aname="nlb-target-type">`service.beta.kubernetes.io/aws-load-balancer-nlb-target-type`</a> specifies the target type to configure for NLB. You can choose between
63
+
`instance` and `ip`.
64
+
- `instance` mode will route traffic to all EC2 instances within cluster on the [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport) opened for your service.
65
+
66
+
!!!note ""
67
+
service must be of type "NodePort" or "LoadBalancer" for `instance` targets
68
+
69
+
- `ip` mode will route traffic directly to the pod IP.
70
+
71
+
!!!note ""
72
+
network plugin must use native AWS VPC networking configuration for pod IP, for example [Amazon VPC CNI plugin](https://github.com/aws/amazon-vpc-cni-k8s).
- <aname="subnets">`service.beta.kubernetes.io/aws-load-balancer-subnets`</a> specifies the [Availability Zone](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html)
45
80
the NLB will route traffic to. See [Network Load Balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#availability-zones) for more details.
46
81
@@ -58,6 +93,7 @@ the NLB will route traffic to. See [Network Load Balancers](https://docs.aws.ama
- <aname="alpn-policy">`service.beta.kubernetes.io/aws-load-balancer-alpn-policy`</a> allows you to configure the [ALPN policies](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-tls-listener.html#alpn-policies)
- <aname="target-node-labels">`service.beta.kubernetes.io/aws-load-balancer-target-node-labels`</a> specifies which nodes to include in the target group registration for `instance` target type.
NLB target group attributes can be controlled via the following annotations:
123
+
NLB resource attributes can be controlled via the following annotations:
81
124
82
125
- <aname="proxy-protocol-v2">service.beta.kubernetes.io/aws-load-balancer-proxy-protocol</a> specifies whether to enable proxy protocol v2 on the target group.
83
126
Set to '*' to enable proxy protocol v2. This annotation takes precedence over the annotation `service.beta.kubernetes.io/aws-load-balancer-target-group-attributes`
@@ -109,4 +152,33 @@ for proxy protocol v2 configuration.
109
152
- enable [client IP preservation](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html#client-ip-preservation)
0 commit comments