chore: add procedure to enable vpc_v3 in older kapsule clusters (#4740)

* chore: add procedure to enable vpc_v3 in older kapsule clusters

* apply suggestions

Co-authored-by: Rowena Jones <[email protected]>

* apply suggestions

Co-authored-by: Néda <[email protected]>

---------

Co-authored-by: Rowena Jones <[email protected]>
Co-authored-by: Néda <[email protected]>

Author: 3 people

pages/kubernetes/how-to/manage-allowed-ips.mdx

@@ -22,6 +22,9 @@ The default entry `0.0.0.0/0` enables any host to establish a connection.
 - A Scaleway account logged into the [Scaleway console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing actions in the intended Organization
 - [Created](/kubernetes/how-to/create-cluster) a Kubernetes Kapsule or Kosmos cluster
+<Message type="tip">
+  Every cluster created after March 8th 2025 has this feature enabled by default. If you do not see the **Network** tab in your cluster's dashboard in the Scaleway console, then the feature is not enabled on your cluster. You can [open a support ticket](https://console.scaleway.com/support/tickets/create) to have it enabled manually.
+</Message>
 
 <Message type="note">
   Allowed IP configuration is available for [fully isolated Kapsule clusters](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation), and Kosmos clusters.