Skip to content

Commit cf7d5c1

Browse files
committed
add commands to see webhooks on cluster
1 parent ae463d3 commit cf7d5c1

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

latest/ug/nodes/hybrid-nodes-webhooks.adoc

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ There are several techniques you can use to make your on-premises pod CIDR routa
1919

2020
If you _cannot_ make your on-premises pod CIDR routable on your on-premises network and need to run webhooks, it is recommended to run webhooks on EC2 instances in the same EKS cluster as your hybrid nodes.
2121

22+
[#hybrid-nodes-considerations-mixed-mode]
2223
== Considerations for mixed mode clusters
2324

2425
Mixed mode clusters are defined as EKS clusters that have both hybrid nodes and nodes running in {aws} Cloud. When running a mixed mode cluster, consider the following recommendations:
@@ -34,6 +35,18 @@ Mixed mode clusters are defined as EKS clusters that have both hybrid nodes and
3435
[#hybrid-nodes-mixed-mode]
3536
== Configure add-ons and webhooks for mixed mode clusters
3637

38+
To view the mutating and validating webhooks running on your cluster, you can view the *Extensions* resource type in the *Resources* panel of the EKS console for your cluster, or you can use the following commands.
39+
40+
[source,bash,subs="verbatim,attributes"]
41+
----
42+
kubectl get mutatingwebhookconfigurations
43+
----
44+
45+
[source,bash,subs="verbatim,attributes"]
46+
----
47+
kubectl get validatingwebhookconfigurations
48+
----
49+
3750
[#hybrid-nodes-mixed-coredns]
3851
=== Configure CoreDNS replicas
3952

0 commit comments

Comments
 (0)