Did you follow this guide?

I think the mysql-deployment.yaml file uses mysql 5.6, and when I tried to modify that to use mysql 8.0, it worked.

BTW if you are not using "default" namespace to run Joget, then you need to modify the "ClusterRoleBinding" kind in the joget-dx8-tomcat9-deployment.yaml file. Update the namespace according to your environment.

THANKS!

Fixing the ClusterRoleBinding got me to the next issue that needs fixing. We are using our own namespace.

I found and worked around the issue.

A post on one of the SM sites mentioned that fsGroup and securityContext in Kubernetes only works for emptyDir volume mounts. HostPath persistent volumes are created as root with 0600 for chmod permissions, and most implementations of Pod Security Policies, and apparently the later Pod Security Admission, ignore fsGroup changes on such PVs (chown and chmod just no-op and ignore the request).

The workaround is to remove the hostPath definition that created the pod folder /mnt/data from the PV resource. That let me configure the database and get to the home screen. Connecting to the pod showed the permissions on the mounted PV were correct.