Skip to content

Commit 3e87666

Browse files
committed
chore(mks/know-limits): subnet's nameserver ignored
1 parent 4a5b10d commit 3e87666

File tree

1 file changed

+1
-1
lines changed
  • pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits

1 file changed

+1
-1
lines changed

pages/public_cloud/containers_orchestration/managed_kubernetes/known-limits/guide.en-ie.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ The `vRack` feature is currently available and compliant with our Managed Kubern
137137
To prevent any conflict, we advise you to keep `DHCP` service running in your private network.
138138

139139
> [!warning]
140-
> If you create your subnet via the [OVHcloud APIv6](https://api.ovh.com/console/#/cloud/project/{serviceName}/network/private/{networkId}/subnet#POST), please ensure that this option `noGateway` is checked if you do not have a gateway on this subnet. Not doing so will result in faulty services of type LoadBalancer.
140+
> At the moment, MKS worker nodes cannot use provided Subnet's DNS nameservers.
141141
>
142142
143143
> [!warning]

0 commit comments

Comments
 (0)