managing-max-pods.adoc Documentation implies that podsPerCore can be used alone but actually maxPods must also be set

Create a KubeletConfig with a podsPerCore value that would total to more than 250 on a worker but without maxPods. The result is that a worker would still be limited to 250 Pods.

1. Create a KubeletConfig with a podsPerCore value that would total to more than 250 on a worker
2. Don't set maxPods
3. Wait for worker Nodes to be restarted
4. Try to deploy more than 250 running Pods to a worker Node.

Kubernetes will refuse to assign more than 250 Pods.

If reading the documentation, one would expect podsPerCore to be enough to overwrite the 250 default limit per Node when when enough CPU cores are present on a worker.