(DOCSP-18055): -cert to -pem for tls filenames

Author: jwilliams-mongo

source/includes/prereqs/custom-ca-prereqs-naming-conventions.rst

@@ -11,5 +11,5 @@
 
      - Replace ``<X>`` with the member of a shard or replica set.
 
-   - End the files with ``-cert`` and *not* ``.cert``.
+   - End the files with ``-pem`` and *not* ``.pem``.
      These files shouldn't have a file extension.

source/includes/prereqs/custom-ca-prereqs-rs-tls-only.rst

@@ -9,7 +9,7 @@
      * - Your custom |certauth|
        - ``ca-pem``
      * - Each member of your replica set
-       - ``<metadata.name>-<X>-cert``
+       - ``<metadata.name>-<X>-pem``
 
   .. include:: /includes/prereqs/pem-file-description.rst
 

source/includes/prereqs/custom-ca-prereqs-rs-tls-x509-internal.rst

@@ -9,7 +9,7 @@
      * - Your custom |certauth|
        - ``ca-pem``
      * - Each member of your replica set
-       - ``<metadata.name>-<X>-cert``
+       - ``<metadata.name>-<X>-pem``
      * - Your project's Automation or MongoDB Agent
        - ``mms-automation-agent-pem``
      * - Your project's Backup Agent (if needed)

source/includes/prereqs/custom-ca-prereqs-sc-tls-only.rst

@@ -9,10 +9,10 @@
      * - Your custom |certauth|
        - ``ca-pem``
      * - Each shard in your sharded cluster
-       - ``<metadata.name>-<Y>-<X>-cert``
+       - ``<metadata.name>-<Y>-<X>-pem``
      * - Each member of your config server replica set
-       - ``<metadata.name>-config-<X>-cert``
+       - ``<metadata.name>-config-<X>-pem``
      * - Each |mongos|
-       - ``<metadata.name>-mongos-<X>-cert``
+       - ``<metadata.name>-mongos-<X>-pem``
 
   .. include:: /includes/prereqs/custom-ca-prereqs-naming-conventions.rst

source/includes/prereqs/custom-ca-prereqs-sc-tls-x509-internal.rst

@@ -9,11 +9,11 @@
      * - Your custom |certauth|
        - ``ca-pem``
      * - Each shard in your sharded cluster
-       - ``<metadata.name>-<Y>-<X>-cert``
+       - ``<metadata.name>-<Y>-<X>-pem``
      * - Each member of your config server replica set
-       - ``<metadata.name>-config-<X>-cert``
+       - ``<metadata.name>-config-<X>-pem``
      * - Each |mongos|
-       - ``<metadata.name>-mongos-<X>-cert``
+       - ``<metadata.name>-mongos-<X>-pem``
      * - Your project's Automation or MongoDB Agent
        - ``mms-automation-agent-pem``
      * - Your project's Backup Agent (if needed)

source/includes/prereqs/custom-ca-prereqs.rst

@@ -9,18 +9,18 @@
      * - Your custom |certauth|
        - ``ca-pem``
      * - Each member of your replica set
-       - ``<metadata.name>-<X>-cert``
+       - ``<metadata.name>-<X>-pem``
      * - Your project's Automation or MongoDB Agent
        - ``mms-automation-agent-pem``
      * - Your project's Backup Agent (if needed)
        - ``mms-backup-agent-pem``
      * - Your project's Monitoring Agent (if needed)
        - ``mms-monitoring-agent-pem``
      * - Each shard in your sharded cluster
-       - ``<metadata.name>-<Y>-<X>-cert``
+       - ``<metadata.name>-<Y>-<X>-pem``
      * - Each member of your config server replica set
-       - ``<metadata.name>-config-<X>-cert``
+       - ``<metadata.name>-config-<X>-pem``
      * - Each |mongos|
-       - ``<metadata.name>-mongos-<X>-cert``
+       - ``<metadata.name>-mongos-<X>-pem``
 
   .. include:: /includes/prereqs/custom-ca-prereqs-naming-conventions.rst

source/includes/steps-source-deploy-k8s-resource.yaml

@@ -1023,9 +1023,9 @@ content: |
   .. code-block:: sh
 
      kubectl create secret generic <metadata.name>-cert \
-       --from-file=<metadata.name>-0-cert \
-       --from-file=<metadata.name>-1-cert \
-       --from-file=<metadata.name>-2-cert
+       --from-file=<metadata.name>-0-pem \
+       --from-file=<metadata.name>-1-pem \
+       --from-file=<metadata.name>-2-pem
 
   This example covers a three-member replica set. If you have more than
   three members, you can add them to the certificate using the
@@ -1044,9 +1044,9 @@ content: |
   .. code-block:: sh
 
      kubectl create secret generic <metadata.name>-cert \
-       --from-file=<metadata.name>-0-cert \
-       --from-file=<metadata.name>-1-cert \
-       --from-file=<metadata.name>-2-cert \
+       --from-file=<metadata.name>-0-pem \
+       --from-file=<metadata.name>-1-pem \
+       --from-file=<metadata.name>-2-pem \
        --dry-run=client \
         -o yaml |
      kubectl apply -f -
@@ -1068,9 +1068,9 @@ content: |
   .. code-block:: sh
 
      kubectl create secret generic <metadata.name>-clusterfile \
-       --from-file=<metadata.name>-0-cert \
-       --from-file=<metadata.name>-1-cert \
-       --from-file=<metadata.name>-2-cert
+       --from-file=<metadata.name>-0-pem \
+       --from-file=<metadata.name>-1-pem \
+       --from-file=<metadata.name>-2-pem
 
   This example covers a three-member replica set. If you have more than
   three members, you can add them to the certificate using the
@@ -1089,9 +1089,9 @@ content: |
   .. code-block:: sh
 
      kubectl create secret generic <metadata.name>-clusterfile \
-       --from-file=<metadata.name>-0-cert \
-       --from-file=<metadata.name>-1-cert \
-       --from-file=<metadata.name>-2-cert \
+       --from-file=<metadata.name>-0-pem \
+       --from-file=<metadata.name>-1-pem \
+       --from-file=<metadata.name>-2-pem \
        --dry-run=client \
         -o yaml |
      kubectl apply -f -
@@ -1127,18 +1127,18 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-0-cert \
-            --from-file=<metadata.name>-0-0-cert \
-            --from-file=<metadata.name>-0-1-cert \
-            --from-file=<metadata.name>-0-2-cert \
-            --from-file=<metadata.name>-0-3-cert \
-            --from-file=<metadata.name>-0-4-cert
+            --from-file=<metadata.name>-0-0-pem \
+            --from-file=<metadata.name>-0-1-pem \
+            --from-file=<metadata.name>-0-2-pem \
+            --from-file=<metadata.name>-0-3-pem \
+            --from-file=<metadata.name>-0-4-pem
 
      kubectl -n mongodb create secret generic <metadata.name>-1-cert \
-            --from-file=<metadata.name>-1-0-cert \
-            --from-file=<metadata.name>-1-1-cert \
-            --from-file=<metadata.name>-1-2-cert \
-            --from-file=<metadata.name>-1-3-cert \
-            --from-file=<metadata.name>-1-4-cert
+            --from-file=<metadata.name>-1-0-pem \
+            --from-file=<metadata.name>-1-1-pem \
+            --from-file=<metadata.name>-1-2-pem \
+            --from-file=<metadata.name>-1-3-pem \
+            --from-file=<metadata.name>-1-4-pem
 
   This example covers a two-shard sharded cluster with five members per
   shard. If you have more than two shards or five members per shard,
@@ -1157,21 +1157,21 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-0-cert \
-            --from-file=<metadata.name>-0-0-cert \
-            --from-file=<metadata.name>-0-1-cert \
-            --from-file=<metadata.name>-0-2-cert \
-            --from-file=<metadata.name>-0-3-cert \
-            --from-file=<metadata.name>-0-4-cert \
+            --from-file=<metadata.name>-0-0-pem \
+            --from-file=<metadata.name>-0-1-pem \
+            --from-file=<metadata.name>-0-2-pem \
+            --from-file=<metadata.name>-0-3-pem \
+            --from-file=<metadata.name>-0-4-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -
 
      kubectl -n mongodb create secret generic <metadata.name>-1-cert \
-            --from-file=<metadata.name>-1-0-cert \
-            --from-file=<metadata.name>-1-1-cert \
-            --from-file=<metadata.name>-1-2-cert \
-            --from-file=<metadata.name>-1-3-cert \
-            --from-file=<metadata.name>-1-4-cert \
+            --from-file=<metadata.name>-1-0-pem \
+            --from-file=<metadata.name>-1-1-pem \
+            --from-file=<metadata.name>-1-2-pem \
+            --from-file=<metadata.name>-1-3-pem \
+            --from-file=<metadata.name>-1-4-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -
@@ -1193,9 +1193,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-config-cert \
-            --from-file=<metadata.name>-config-0-cert \
-            --from-file=<metadata.name>-config-1-cert \
-            --from-file=<metadata.name>-config-2-cert
+            --from-file=<metadata.name>-config-0-pem \
+            --from-file=<metadata.name>-config-1-pem \
+            --from-file=<metadata.name>-config-2-pem
 
 ---
 title: "Renew the |k8s-secret| for your config server's TLS certificates."
@@ -1210,9 +1210,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-config-cert \
-            --from-file=<metadata.name>-config-0-cert \
-            --from-file=<metadata.name>-config-1-cert \
-            --from-file=<metadata.name>-config-2-cert \
+            --from-file=<metadata.name>-config-0-pem \
+            --from-file=<metadata.name>-config-1-pem \
+            --from-file=<metadata.name>-config-2-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -
@@ -1230,9 +1230,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-mongos-cert \
-            --from-file=<metadata.name>-mongos-0-cert \
-            --from-file=<metadata.name>-mongos-1-cert \
-            --from-file=<metadata.name>-mongos-2-cert
+            --from-file=<metadata.name>-mongos-0-pem \
+            --from-file=<metadata.name>-mongos-1-pem \
+            --from-file=<metadata.name>-mongos-2-pem
 
 ---
 title: "Renew the |k8s-secret| for your mongos server's TLS certificates."
@@ -1247,9 +1247,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-mongos-cert \
-            --from-file=<metadata.name>-mongos-0-cert \
-            --from-file=<metadata.name>-mongos-1-cert \
-            --from-file=<metadata.name>-mongos-2-cert \
+            --from-file=<metadata.name>-mongos-0-pem \
+            --from-file=<metadata.name>-mongos-1-pem \
+            --from-file=<metadata.name>-mongos-2-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -
@@ -1267,18 +1267,18 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-0-clusterfile \
-            --from-file=<metadata.name>-0-0-cert \
-            --from-file=<metadata.name>-0-1-cert \
-            --from-file=<metadata.name>-0-2-cert \
-            --from-file=<metadata.name>-0-3-cert \
-            --from-file=<metadata.name>-0-4-cert
+            --from-file=<metadata.name>-0-0-pem \
+            --from-file=<metadata.name>-0-1-pem \
+            --from-file=<metadata.name>-0-2-pem \
+            --from-file=<metadata.name>-0-3-pem \
+            --from-file=<metadata.name>-0-4-pem
 
      kubectl -n mongodb create secret generic <metadata.name>-1-clusterfile \
-            --from-file=<metadata.name>-1-0-cert \
-            --from-file=<metadata.name>-1-1-cert \
-            --from-file=<metadata.name>-1-2-cert \
-            --from-file=<metadata.name>-1-3-cert \
-            --from-file=<metadata.name>-1-4-cert
+            --from-file=<metadata.name>-1-0-pem \
+            --from-file=<metadata.name>-1-1-pem \
+            --from-file=<metadata.name>-1-2-pem \
+            --from-file=<metadata.name>-1-3-pem \
+            --from-file=<metadata.name>-1-4-pem
 
   This example covers a two-shard sharded cluster with five members per
   shard. If you have more than two shards or five members per shard,
@@ -1297,21 +1297,21 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-0-clusterfile \
-            --from-file=<metadata.name>-0-0-cert \
-            --from-file=<metadata.name>-0-1-cert \
-            --from-file=<metadata.name>-0-2-cert \
-            --from-file=<metadata.name>-0-3-cert \
-            --from-file=<metadata.name>-0-4-cert \
+            --from-file=<metadata.name>-0-0-pem \
+            --from-file=<metadata.name>-0-1-pem \
+            --from-file=<metadata.name>-0-2-pem \
+            --from-file=<metadata.name>-0-3-pem \
+            --from-file=<metadata.name>-0-4-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -
 
      kubectl -n mongodb create secret generic <metadata.name>-1-clusterfile \
-            --from-file=<metadata.name>-1-0-cert \
-            --from-file=<metadata.name>-1-1-cert \
-            --from-file=<metadata.name>-1-2-cert \
-            --from-file=<metadata.name>-1-3-cert \
-            --from-file=<metadata.name>-1-4-cert \
+            --from-file=<metadata.name>-1-0-pem \
+            --from-file=<metadata.name>-1-1-pem \
+            --from-file=<metadata.name>-1-2-pem \
+            --from-file=<metadata.name>-1-3-pem \
+            --from-file=<metadata.name>-1-4-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -
@@ -1333,9 +1333,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-config-clusterfile \
-            --from-file=<metadata.name>-config-0-cert \
-            --from-file=<metadata.name>-config-1-cert \
-            --from-file=<metadata.name>-config-2-cert
+            --from-file=<metadata.name>-config-0-pem \
+            --from-file=<metadata.name>-config-1-pem \
+            --from-file=<metadata.name>-config-2-pem
 
 ---
 title: "Renew the |k8s-secret| for your config server's X.509 certificates."
@@ -1350,9 +1350,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-config-clusterfile \
-            --from-file=<metadata.name>-config-0-cert \
-            --from-file=<metadata.name>-config-1-cert \
-            --from-file=<metadata.name>-config-2-cert \
+            --from-file=<metadata.name>-config-0-pem \
+            --from-file=<metadata.name>-config-1-pem \
+            --from-file=<metadata.name>-config-2-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -
@@ -1370,9 +1370,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-mongos-clusterfile \
-            --from-file=<metadata.name>-mongos-0-cert \
-            --from-file=<metadata.name>-mongos-1-cert \
-            --from-file=<metadata.name>-mongos-2-cert
+            --from-file=<metadata.name>-mongos-0-pem \
+            --from-file=<metadata.name>-mongos-1-pem \
+            --from-file=<metadata.name>-mongos-2-pem
 
 ---
 title: "Renew the |k8s-secret| for your mongos server's X.509 certificates."
@@ -1387,9 +1387,9 @@ content: |
   .. code-block:: sh
 
      kubectl -n mongodb create secret generic <metadata.name>-mongos-clusterfile \
-            --from-file=<metadata.name>-mongos-0-cert \
-            --from-file=<metadata.name>-mongos-1-cert \
-            --from-file=<metadata.name>-mongos-2-cert \
+            --from-file=<metadata.name>-mongos-0-pem \
+            --from-file=<metadata.name>-mongos-1-pem \
+            --from-file=<metadata.name>-mongos-2-pem \
             --dry-run=client \
              -o yaml |
      kubectl apply -f -

source/includes/steps-source-deploy-om-resource.yaml

@@ -7,7 +7,7 @@ content: |
 
   Verify that each member of the Replica Set has one |tls| certificate named with the following format:
 
-  ``<resource-name>-db-<index>-cert``
+  ``<resource-name>-db-<index>-pem``
 
   Where ``<index>`` is a 0-based index number to the total amount of
   members minus one. (``0`` to ``n-1``)
@@ -24,9 +24,9 @@ content: |
   .. code-block:: sh
 
      kubectl create secret generic appdb-cert \
-             --from-file=om-appdb-tls-enabled-db-0-cert \
-             --from-file=om-appdb-tls-enabled-db-1-cert \
-             --from-file=om-appdb-tls-enabled-db-2-cert
+             --from-file=om-appdb-tls-enabled-db-0-pem \
+             --from-file=om-appdb-tls-enabled-db-1-pem \
+             --from-file=om-appdb-tls-enabled-db-2-pem
 
   ``kubectl`` creates one Secret containing the three certificates.