Looks like using K8s 1.25 will have to wait for postgres-operator 1.9. While I'm not seeing the same postgres startup issue as reported when running the 1.8.2 operator on K8s v1.25, our db-init job keeps crash looping and reporting authentication failed for galaxydbuser in the log. Meanwhile, the chart continues to deploy fine with the operator on 1.24 as well as without the operator. Other than that, I don't have other leads as to why it won't run on 1.25.
Looks like using K8s 1.25 will have to wait for postgres-operator 1.9. While I'm not seeing the same postgres startup issue as reported when running the 1.8.2 operator on K8s v1.25, our db-init job keeps crash looping and reporting authentication failed for galaxydbuser in the log. Meanwhile, the chart continues to deploy fine with the operator on 1.24 as well as without the operator. Other than that, I don't have other leads as to why it won't run on 1.25.