diff --git a/docs/_sidebar.md b/docs/_sidebar.md
index e0a5bab8766c6f5bf872f870d824688959408505..52cbe5eb410ddeb852195fbe59d8b6bb5931de26 100644
--- a/docs/_sidebar.md
+++ b/docs/_sidebar.md
@@ -15,7 +15,7 @@
   * [Ansible](/docs/ansible/ansible.md)
   * [Ansible Collection](/docs/ansible/ansible_collection.md)
   * [Vars](/docs/ansible/vars.md)
-* Cloud Providers
+* Cloud Providers (deprecated)
   * [Aws](/docs/cloud_providers/aws.md)
   * [Azure](/docs/cloud_providers/azure.md)
   * [Cloud](/docs/cloud_providers/cloud.md)
diff --git a/docs/advanced/gcp-lb.md b/docs/advanced/gcp-lb.md
index 8e8f8c427b0f98800c05a1bb608a781789c8f026..80369186a34a66d07e1a915d134a5ea4eac9e996 100644
--- a/docs/advanced/gcp-lb.md
+++ b/docs/advanced/gcp-lb.md
@@ -1,5 +1,7 @@
 # GCP Load Balancers for type=LoadBalacer of Kubernetes Services
 
+> **Removed**: Since v1.31 (the Kubespray counterpart is v2.27), Kubernetes no longer supports `cloud_provider`. (except external cloud provider)
+
 Google Cloud Platform can be used for creation of Kubernetes Service Load Balancer.
 
 This feature is able to deliver by adding parameters to `kube-controller-manager` and `kubelet`. You need specify:
diff --git a/docs/cloud_providers/aws.md b/docs/cloud_providers/aws.md
index 45938980c3eadfa29d76b8355b45b446b4b8d2a7..41706fdd5688e76b9be8ff2f5b90de3e5af072e0 100644
--- a/docs/cloud_providers/aws.md
+++ b/docs/cloud_providers/aws.md
@@ -1,5 +1,7 @@
 # AWS
 
+> **Removed**: Since v1.31 (the Kubespray counterpart is v2.27), Kubernetes no longer supports `cloud_provider`. (except external cloud provider)
+
 To deploy kubespray on [AWS](https://aws.amazon.com/) uncomment the `cloud_provider` option in `group_vars/all.yml` and set it to `'aws'`. Refer to the [Kubespray Configuration](#kubespray-configuration) for customizing the provider.
 
 Prior to creating your instances, you **must** ensure that you have created IAM roles and policies for both "kubernetes-master" and "kubernetes-node". You can find the IAM policies [here](https://github.com/kubernetes-sigs/kubespray/tree/master/contrib/aws_iam/). See the [IAM Documentation](https://aws.amazon.com/documentation/iam/) if guidance is needed on how to set these up. When you bring your instances online, associate them with the respective IAM role. Nodes that are only to be used for Etcd do not need a role.
diff --git a/docs/cloud_providers/azure.md b/docs/cloud_providers/azure.md
index a164ea757011818ef488d569f0d1cd39ebe06f8d..50d2f1d1c2b2c43125c9da298d1a25e6b0338b33 100644
--- a/docs/cloud_providers/azure.md
+++ b/docs/cloud_providers/azure.md
@@ -1,5 +1,7 @@
 # Azure
 
+> **Removed**: Since v1.31 (the Kubespray counterpart is v2.27), Kubernetes no longer supports `cloud_provider`. (except external cloud provider)
+
 To deploy Kubernetes on [Azure](https://azure.microsoft.com) uncomment the `cloud_provider` option in `group_vars/all/all.yml` and set it to `'azure'`.
 
 All your instances are required to run in a resource group and a routing table has to be attached to the subnet your instances are in.
diff --git a/docs/cloud_providers/cloud.md b/docs/cloud_providers/cloud.md
index d7fcfef7fdc9b1c1032b583953e0493bba64002c..d88a3aeccc6ad043053d5a9b1f7f0a16c9dabc36 100644
--- a/docs/cloud_providers/cloud.md
+++ b/docs/cloud_providers/cloud.md
@@ -1,5 +1,7 @@
 # Cloud providers
 
+> **Removed**: Since v1.31 (the Kubespray counterpart is v2.27), Kubernetes no longer supports `cloud_provider`. (except external cloud provider)
+
 ## Provisioning
 
 You can deploy instances in your cloud environment in several ways. Examples include Terraform, Ansible (ec2 and gce modules), and manual creation.