Steps to install Camunda Platform 8 on AWS EKS using Helm charts

Hi, does anyone have any experience in setting up Camunda platform 8 self managed in AWS EKS cluster using Camunda’s provided helm charts?

Have you had any luck with this? I am beating my way thru it as well. Right now I am at this level of “completeness”

% kubectl get pods
NAME                                           READY   STATUS             RESTARTS         AGE
camunda-stage-identity-6fcfdcc594-vqzbc        0/1     CrashLoopBackOff   14 (27s ago)     56m
camunda-stage-keyclo-0                         0/1     Running            14 (5m30s ago)   56m
camunda-stage-operate-848ff76798-wmrmf         1/1     Running            0                56m
camunda-stage-optimize-cd77d686c-nwfqt         1/1     Running            0                56m
camunda-stage-postgresql-0                     1/1     Running            0                56m
camunda-stage-tasklist-5cf7955c86-cddvp        1/1     Running            0                56m
camunda-stage-zeebe-0                          1/1     Running            0                56m
camunda-stage-zeebe-1                          1/1     Running            0                56m
camunda-stage-zeebe-2                          1/1     Running            0                56m
camunda-stage-zeebe-gateway-6b8bffc79f-4rpgj   1/1     Running            0                56m
camunda-stage-zeebe-gateway-6b8bffc79f-rc4ww   1/1     Running            0                56m
elasticsearch-master-0                         1/1     Running            0                56m
elasticsearch-master-1                         1/1     Running            0                56m

the identity and keycloak pods keep crashing …
i can tail the logs before (of keycloak) the crash which is a java RT exception null pointer.

14:03:23,724 INFO  [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (ServerService Thread Pool -- 65) Node name: camunda-stage-keyclo-0, Site name: null
14:03:24,794 WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 65) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
        at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:364)
        at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:371)
        at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
        at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1328)
        at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:505)
        at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:640)
        at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:605)
        at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
        at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
        at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)

but I dont know that values.yaml to pass in is required to set this value