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/targetgroupbinding/targetgroupbinding.md
+9-2Lines changed: 9 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,8 @@ This will allow you to provision the load balancer infrastructure completely out
5
5
6
6
!!!tip "usage to support Ingress and Service"
7
7
The AWS LoadBalancer controller internally used TargetGroupBinding to support the functionality for Ingress and Service resource as well.
8
-
It automatically creates TargetGroupBinding in the same namespace of the Service used.
9
-
8
+
It automatically creates TargetGroupBinding in the same namespace of the Service used.
9
+
10
10
You can view all TargetGroupBindings in a namespace by `kubectl get targetgroupbindings -n <your-namespace> -o wide`
11
11
12
12
@@ -17,6 +17,13 @@ TargetGroupBinding CR supports TargetGroups of either `instance` or `ip` TargetT
17
17
If TargetType is not explicitly specified, a mutating webhook will automatically call AWS API to find the TargetType for your TargetGroup and set it to correct value.
18
18
19
19
20
+
## VpcId
21
+
TargetGroupBinding CR supports the explicit definition of the Virtual Private Cloud (VPC) of your TargetGroup.
22
+
23
+
!!!tip ""
24
+
If the VpcId is not explicitly specified, a mutating webhook will automatically call AWS API to find the VpcId for your TargetGroup and set it to correct value.
0 commit comments