Vishrant Gupta

Hi @pablogalegoc, when the postgresql pod fails (without network partitioning) and there is one postgresql primary, the pgpool pod restarts: (Almost 1 minute and 20 seconds of downtime/ failover time...

This issue is happening when the primary is going down, even though the standby is still healthy.

I have the same issue. @dead23angel @JiboStore @alexmngn

I have a deployment that gets rendered as: ``` apiVersion: apps/v1 kind: Deployment metadata: annotations: kbld.k14s.io/images: | - Metas: - Tag: 1.7.2-debian-10-r0 Type: resolved URL: harbor-repo.vmware.com/tcx/snapshot/cert-manager:1.7.2-debian-10-r0 URL: harbor-repo.vmware.com/tcx/snapshot/cert-manager@sha256:e48338841039ab23983e9a461add0a6815381bab5a837163eb365fea7a00769b spec: spec:...

Ah! I see the regex is not supported.

Thanks, @jenisys. I am running the scenarios with `--no-capture` how would the implementation of `verify that the logo is visible but do not fail` would look like, how the warning...

Check this answer: https://stackoverflow.com/questions/8746207/1071-specified-key-was-too-long-max-key-length-is-1000-bytes/50689604#50689604

Curious to know when 2.x release is planned.