Closed linghan-hub closed 1 year ago
log of pg has renamed to running, and isn't merged to release-0.4.
this case results from this scenario: 1: use origin helm chart of release-0.4 , and install cluster-definition.yaml which doesn't contain the running-log changes 2: local test uses the new code of main, and generate the resource of cluster.yaml
brief recap, the origin helm chart doesn't keep inconsistent with branch main result in the failure of this installation
The name in the cd should be synchronized to running
code not synced between cluster and clusterdefinition.
local k3d environment
cat 00_postgresqlcluster.yaml
see logs