Skip to content

Commit 19d5bf9

Browse files
authored
chore: add procedure to enable vpc_v3 in older kapsule clusters
1 parent f564877 commit 19d5bf9

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ The default entry `0.0.0.0/0` enables any host to establish a connection.
2222
- A Scaleway account logged into the [Scaleway console](https://console.scaleway.com)
2323
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing actions in the intended Organization
2424
- [Created](/kubernetes/how-to/create-cluster) a Kubernetes Kapsule or Kosmos cluster
25+
<Message type="tip">
26+
Every cluster created after March 8th have this feature enabled by default, you can check if your cluster have it by looking in the console: You should see a `Network` tab in your cluster view. If this is not the case, you can open a support ticket to have it enabled manually.
27+
</Message>
2528

2629
<Message type="note">
2730
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.

0 commit comments

Comments
 (0)