Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[k8s] Activating DHCP on private networks attached to Kapsule clusters
Scheduled Maintenance
Report for Scaleway
Completed
The scheduled maintenance has been completed.
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled
To future-proof the Kubernetes Kapsule managed service and bring you new isolation features, all legacy private networks attached to a Kapsule cluster will have a DHCP activated. Learn more about DHCP https://www.scaleway.com/en/docs/network/vpc/concepts/#dhcp
While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks created prior to July 12 2023.
We recommend users to check our VPC documentation for more information on the feature. https://www.scaleway.com/en/docs/network/vpc/reference-content/vpc-migration/#dhcp-activation-on-pre-existing-private-networks. Find our dedicated documentation on how to activate DHCP https://www.scaleway.com/en/docs/network/vpc/how-to/activate-dhcp/.
Activating DHCP will overwrite any existing manually configured static IP addresses for resources attached to the network.
While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks created prior to July 12 2023.
We recommend users to check our VPC documentation for more information on the feature. https://www.scaleway.com/en/docs/network/vpc/reference-content/vpc-migration/#dhcp-activation-on-pre-existing-private-networks. Find our dedicated documentation on how to activate DHCP https://www.scaleway.com/en/docs/network/vpc/how-to/activate-dhcp/.
Activating DHCP will overwrite any existing manually configured static IP addresses for resources attached to the network.
This scheduled maintenance affected: Elements - Products (Kubernetes Kapsule).