EAP 8 Helm Chart has the default initial delay too big (60 seconds, see https://github.com/jbossas/eap-charts/blob/eap8-dev/charts/eap8/values.yaml#L34). Since the application deployment's Pod can start in less than 20-30 seconds, the container is unnecessarily waiting for another 30 seconds to become ready and the deployment may appear slow to the customers. WF Charts do not have such initial delay (https://github.com/wildfly/wildfly-charts/blob/main/charts/wildfly/values.yaml) This may be fixed by customer by overriding deploy.livenessProbe in their Helm Release value file, however I think the default values should be more fine-grained (e.g by configuring K8S probe properties https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes)