Clarify note on disabling built-in CCM

Co-authored-by: Brad Davidson <brad@oatmail.org>
Signed-off-by: Alex Seymour <alex.seymour@suse.com>

Author: axeal

docs/networking/networking-services.md

@@ -108,7 +108,7 @@ K3s provides an embedded Cloud Controller Manager (CCM) that does the following:
 Before deploying an external CCM, you must start all K3s servers with the `--disable-cloud-controller` flag to disable the embedded CCM. When using an external CCM, node addresses will be provided by cloud provider instance metadata APIs, instead of the K3s flag values.
 
 :::note
-If you disable the built-in CCM and add the `kubelet-arg` `cloud-provider=external`, without deploying and properly configuring an external substitute, nodes will remain tainted and unschedulable.
+If you disable the built-in CCM and set `--kubelet-arg=cloud-provider=external` without deploying and properly configuring an external substitute, nodes will remain tainted and unschedulable. By default, disabling the built-in CCM prevents K3s from setting the kubelet `cloud-provider` arg, which indicates that no cloud provider is in use. Without any cloud-provider, Node Provider-IDs and External Addresses will not be set.
 :::