Detect issues with Kubernetes DNS service IP address during creation
When deploying a Kubernetes cluster, you have the option to enter the Kubernetes DNS service IP address. The UI will allow you to set this to e.g. 172.18.0.1 with no complaints, but then deployment fails because of this with an error saying DNSServiceIP can not be the first IP address in ServiceCidr.
It would be nice if the creation UI flow would already highlight the error and stop me from wasting a fair bit of time waiting for the deployment to fail with the error.