Merge pull request #75082 from bergerhoffer/OCPBUGS-32769

OCPBUGS#32769: Adding dockercfg to list of types of secrets

Author: bergerhoffer

modules/nodes-pods-secrets-about.adoc

@@ -64,10 +64,12 @@ which is the default.
 
 Specify one of the following types to trigger minimal server-side validation to ensure the presence of specific key names in the secret data:
 
-* `kubernetes.io/service-account-token`. Uses a service account token.
-* `kubernetes.io/basic-auth`. Use with Basic Authentication.
-* `kubernetes.io/ssh-auth`. Use with SSH Key Authentication.
-* `kubernetes.io/tls`. Use with TLS certificate authorities.
+* `kubernetes.io/basic-auth`: Use with Basic authentication
+* `kubernetes.io/dockercfg`: Use as an image pull secret
+* `kubernetes.io/dockerconfigjson`: Use as an image pull secret
+* `kubernetes.io/service-account-token`: Use to obtain a legacy service account API token
+* `kubernetes.io/ssh-auth`: Use with SSH key authentication
+* `kubernetes.io/tls`: Use with TLS certificate authorities
 
 Specify `type: Opaque` if you do not want validation, which means the secret does not claim to conform to any convention for key names or values.
 An _opaque_ secret, allows for unstructured `key:value` pairs that can contain arbitrary values.
@@ -78,7 +80,7 @@ You can specify other arbitrary types, such as `example.com/my-secret-type`. The
 but indicate that the creator of the secret intended to conform to the key/value requirements of that type.
 ====
 
-For examples of different secret types, see the code samples in _Using Secrets_.
+For examples of creating different types of secrets, see _Understanding how to create secrets_.
 
 [id="nodes-pods-secrets-about-keys_{context}"]
 == Secret data keys