OSDOCS:13913 Add reason for no Node Disrupt Policy for /etc/containers/registries.conf.d

Author: Michael Burke

modules/machine-config-node-disruption-example.adoc

@@ -55,6 +55,8 @@ status:
   readyReplicas: 0
 ----
 
+The default node disruption policy does not contain a policy for changes to the `/etc/containers/registries.conf.d` file. This is because both {product-title} and {op-system-base-full} use the `registries.conf.d` file to specify aliases for image short names. It is recommended that you always pull an image by its fully-qualified name. This is particularly important with public registries, because the image might not deploy if the public registry requires authentication. You can create a user-defined policy to use with the `/etc/containers/registries.conf.d` file, if you need to use image short names. 
+
 In the following example, when changes are made to the SSH keys, the MCO drains the cluster nodes, reloads the `crio.service`, reloads the systemd configuration, and restarts the `crio-service`.
 
 .Example node disruption policy for an SSH key change