Modify MySQL image used and password flag that changed with version 8.4 (#555)

* modify MySQL image used and password flag that changed

* tweak doc

Author: PingDavidR

30-helm/pingcentral-external-mysql-db/mysql.yaml

@@ -11,8 +11,8 @@ metadata:
   name: mysql-external
 spec:
   ports:
-  - name: https
-    port: 3306
+    - name: https
+      port: 3306
   selector:
     app: mysql
 ---
@@ -25,8 +25,8 @@ metadata:
     app.kubernetes.io/name: mysql
 spec:
   ports:
-  - name: mysql
-    port: 3306
+    - name: mysql
+      port: 3306
   clusterIP: None
   selector:
     app: mysql
@@ -52,12 +52,12 @@ spec:
         app.kubernetes.io/name: mysql
     spec:
       containers:
-      - image: mysql:latest
-        name: mysql
-        args: ["--default-authentication-plugin=mysql_native_password"]
-        env:
-        - name: MYSQL_ROOT_PASSWORD
-          value: 2Federate
-        ports:
-        - containerPort: 3306
-          name: https
+        - image: mysql:8.4
+          name: mysql
+          args: ["--mysql-native-password=ON"]
+          env:
+            - name: MYSQL_ROOT_PASSWORD
+              value: 2Federate
+          ports:
+            - containerPort: 3306
+              name: https

docs/how-to/upgradePingCentral.md

@@ -165,7 +165,7 @@ select * from DATABASECHANGELOG;
     kubectl cp demo-pingcentral-6d4bb97c98-m7vwb:/opt/out/instance/conf/pingcentral.jwk ${HOME}/projects/test-server-profiles/baseline/pingcentral/external-mysql-db/instance/conf/pingcentral.jwk
     ```
 
-1. Check to see that the `pingcentral.jwk` file has been updated in your server-profile and push these changes to your repository.
+1. Check to see that the `pingcentral.jwk` file has been placed in your server-profile and push these changes to your repository.
 
     ```sh
     cd "${HOME}/projects/test-server-profiles"
@@ -178,6 +178,8 @@ select * from DATABASECHANGELOG;
     The pod name from which you copy will vary.
 !!! note "JWK Unique to PingCentral Instance"
     The `pingcentral.jwk` file is used to encrypt and decrypt the PingCentral configuration.  It is unique to each PingCentral instance and must be copied to the new server profile.  Otherwise, the new pod will fail to start.
+!!! note "File copy error"
+    If you receive an notification `tar: removing leading '/' from member names` when copying the file, it can be ignored.
 !!! warning "Security Warning"
     Storing the `pingcentral.jwk` file in the server profile **is not recommended** for production environments.  In a production environment, you would likely use a managed key store service, vault, or other encrypted mechanism.