Keycloak version 26.2.5 and helm charts

Getting advice
,
1

Hello,

I would like your advise.
We have deployed on two environments and now we are deploying a clean new environment.

Infrastructure wise we use mysql 8.x, helm charts and kubernetes and keycloak version 26.2.5

Part of the helm charts is:
`livenessProbe:
enabled: true
httpGet:
path: /health/live
port: *containerPortName
initialDelaySeconds: 11

readinessProbe:
enabled: true
httpGet:
path: /health/ready
port: *containerPortName
initialDelaySeconds: 11
failureThreshold: 1

startupProbe:
enabled: true
httpGet:
path: /health/started
port: *containerPortName
initialDelaySeconds: 11
failureThreshold: 10
periodSeconds: 6`

When setting up with
initialDelaySeconds: 10,
Keycloak database scripts are running up to META-INF/jpa-changelog-1.9.0.xml::1.9.0::mposolda@redhat.com saying that
”ERROR: Can’t DROP ‘FK_93S3P0DIUXAWWQQSA528UBY2Q’; check that column/key exists”, which supposedly has been generated in previous running successfully script.

Setting up to initialDelaySeconds: 11 not always successful for the above reason.
Always is the same failing reason

I am trying to understand why does it happen. Is it really the setup of initialDelaySeconds? Is something that i should consider?

Thank you very much in advance.