issues on kubernetes timescaledb-single chart

[archenroot]

Have a look at Troubleshooting or some Common Issues

Describe the bug
After running
helm upgrade --install timescaledb-single-release --create-namespace --namespace timescaledb -f values.yaml charts/timescaledb-single
with these values.yaml https://gist.github.com/archenroot/7d2eccc353adc6f7e7a75d46fe051b82
Pod won't start getting 2 failing events;

MountVolume.SetUp failed for volume "certificate" : secret "timescaledb-cluster-certificate" not found

Unable to attach or mount volumes: unmounted volumes=[storage-volume timescaledb-scripts pgbackrest-bootstrap wal-volume patroni-config pgbackrest kube-api-access-xbdm9 socket-directory post-init certificate], unattached volumes=[storage-volume timescaledb-scripts pgbackrest-bootstrap wal-volume patroni-config pgbackrest kube-api-access-xbdm9 socket-directory post-init certificate]: timed out waiting for the condition

[archenroot]

Also when I run this command under single; sh generate_kustomization.sh timescaledb-single
The kustomization.yaml file is completely empty

[archenroot]

Ok, closing. I expcected secrets to be part of helm, but its good you separated them. Its just that the script didn't work for me for some reason. I used example customization file form your repo and manually made changes to it. That fixed my issue.

Still if I run your script on my Linux system as following:

zangetsu@andromeda ~/proj/infrastructure/k8s-vagrant-multi-node_archenroot/k8s/timescaledb/timescaledb-kubernetes/charts/timescaledb-single $ sh generate_kustomization.sh timescaledb-single2
sed: can't read ./kustomize/example/kustomization.yaml: No such file or directory
Generating a RSA private key
...........................++++
............................++++
writing new private key to './kustomize/timescaledb-single2/tls.key'
-----
Do you want to configure the backup of your database to S3 (compatible) storage? (y/n)
n
generate_kustomization.sh: line 62: read: `-r': not a valid identifier

Generated a kustomization named timescaledb-single2 in directory ./kustomize/timescaledb-single2.


WARNING: The generated certificate in this directory is self-signed and is only
         fit for development and demonstration purposes.
         The certificate should be replaced by a signed certificate, signed by
         a Certificate Authority (CA) that you trust.


You may now wish to (p)review the files that have been created and further edit
them before deployment.


To preview the deployment of the secrets:

    kubectl kustomize "./kustomize/timescaledb-single2"

Or you may want to install the secrets directly? (y/n)
n

To install these secrets, execute:

    kubectl apply -k "./kustomize/timescaledb-single2"

zangetsu@andromeda ~/proj/infrastructure/k8s-vagrant-multi-node_archenroot/k8s/timescaledb/timescaledb-kubernetes/charts/timescaledb-single $ sh generate_kustomization.sh timescaledb-single2
sed: can't read ./kustomize/example/kustomization.yaml: No such file or directory
Generating a RSA private key
...........................++++
............................++++
writing new private key to './kustomize/timescaledb-single2/tls.key'
-----
Do you want to configure the backup of your database to S3 (compatible) storage? (y/n)
n
generate_kustomization.sh: line 62: read: `-r': not a valid identifier

Generated a kustomization named timescaledb-single2 in directory ./kustomize/timescaledb-single2.


WARNING: The generated certificate in this directory is self-signed and is only
         fit for development and demonstration purposes.
         The certificate should be replaced by a signed certificate, signed by
         a Certificate Authority (CA) that you trust.


You may now wish to (p)review the files that have been created and further edit
them before deployment.


To preview the deployment of the secrets:

    kubectl kustomize "./kustomize/timescaledb-single2"

Or you may want to install the secrets directly? (y/n)
n

To install these secrets, execute:

    kubectl apply -k "./kustomize/timescaledb-single2"

It results to generated folder, but the yaml file itself is empty:

[edchow]

I'm getting the same issue with the empty kustomization.yaml file

kubectl apply -k "./kustomize/timescaledb"
error: no objects passed to apply

[edchow]

oh, it looks like the shell script expected me to clone the whole repo or at least the example directory and run it. I just copied the contents of the example file over manually and made some edits like archenroot did

https://github.com/timescale/timescaledb-kubernetes/blob/master/charts/timescaledb-single/kustomize/example/kustomization.yaml