From 2081cc5a6588690b611ef98daec5f44d30519d72 Mon Sep 17 00:00:00 2001
From: punkwalker <126026317+punkwalker@users.noreply.github.com>
Date: Wed, 26 Jul 2023 14:21:09 -0700
Subject: [PATCH] Add warning in doc for ServiceMutatorWebhook (#3180)

This change adds a warning in install documentation about the new Service Mutating Webhook which will set  `spec.loadBalancerClass` field of service type LoadBalancer.
---
 docs/deploy/installation.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/deploy/installation.md b/docs/deploy/installation.md
index 77e79251b..61aa5d0d9 100644
--- a/docs/deploy/installation.md
+++ b/docs/deploy/installation.md
@@ -7,6 +7,11 @@ The LBC is supported by AWS. Some clusters may be using the legacy "in-tree" fun
 !!!question "Existing AWS ALB Ingress Controller users"
     The AWS ALB Ingress controller must be uninstalled before installing the AWS Load Balancer Controller.
     Please follow our [migration guide](upgrade/migrate_v1_v2.md) to do a migration.
+    
+!!!warning "When using AWS Load Balancer Controller v2.5+"
+    The AWS LBC provides a mutating webhook for service resources to set the `spec.loadBalancerClass` field for service of type LoadBalancer on create. 
+    This makes the AWS LBC the **default controller for service** of type LoadBalancer. You can disable this feature and revert to set Cloud Controller Manager (in-tree controller) as the default by setting the helm chart value **enableServiceMutatorWebhook to false** with `--set enableServiceMutatorWebhook=false` . 
+    You will no longer be able to provision new Classic Load Balancer (CLB) from your kubernetes service unless you disable this feature. Existing CLB will continue to work fine.
 
 ## Supported Kubernetes versions
 * AWS Load Balancer Controller v2.0.0~v2.1.3 requires Kubernetes 1.15+