search

timescale / helm-charts

Configuration and Documentation to run TimescaleDB in your Kubernetes cluster
Apache License 2.0
264 stars 223 forks source link

[ISSUE] Unable to run the multi-node timescaledb setup on minikube #363

Closed ashwinphatak closed 2 years ago

ashwinphatak commented 2 years ago

Describe the bug

Unable to run the multi-node timescaledb setup on minikube

To Reproduce

Check out the latest release (https://github.com/timescale/timescaledb-kubernetes/tree/v0.10.0/charts/timescaledb-multinode#installing) and run the following:

helm upgrade --install my-release .

Expected behavior

A multi-node timescaledb instance should get created successfully

Deployment

Didn't use one; followed the instructions in the release README.

v0.10.0

minikube

Deployment Please share some details of what is in your Kubernetes environment, for example:

kubectl get all,secret,configmap,endpoints,pvc -L role -l release=$RELEASE

NAME                                      READY   STATUS                  RESTARTS   AGE   ROLE
pod/attachdn-my-release-db0-data0-x72g5   1/1     Running                 0          10m
pod/attachdn-my-release-db0-data1-6lbkd   1/1     Running                 0          10m
pod/attachdn-my-release-db0-data2-s56v5   1/1     Running                 0          10m
pod/attachdn-my-release-db1-data0-4pnsc   1/1     Running                 0          10m
pod/attachdn-my-release-db1-data1-pxrlz   1/1     Running                 0          10m
pod/attachdn-my-release-db1-data2-8fxh5   1/1     Running                 0          10m
pod/createdb-my-release-db0-tr5f5         1/1     Running                 0          10m
pod/createdb-my-release-db1-zmjg2         1/1     Running                 0          10m
pod/my-release-timescaledb-access-0       0/1     Init:ImagePullBackOff   0          10m
pod/my-release-timescaledb-data-0         0/1     Init:ImagePullBackOff   0          10m
pod/my-release-timescaledb-data-1         0/1     Init:ImagePullBackOff   0          10m
pod/my-release-timescaledb-data-2         0/1     Init:ImagePullBackOff   0          10m

NAME                                  TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE   ROLE
service/my-release-timescaledb        LoadBalancer   10.99.251.204   <pending>     5432:31969/TCP   10m
service/my-release-timescaledb-data   ClusterIP      None            <none>        5432/TCP         10m

NAME                                             READY   AGE   ROLE
statefulset.apps/my-release-timescaledb-access   0/1     10m
statefulset.apps/my-release-timescaledb-data     0/3     10m

NAME                                      COMPLETIONS   DURATION   AGE   ROLE
job.batch/attachdn-my-release-db0-data0   0/1           10m        10m
job.batch/attachdn-my-release-db0-data1   0/1           10m        10m
job.batch/attachdn-my-release-db0-data2   0/1           10m        10m
job.batch/attachdn-my-release-db1-data0   0/1           10m        10m
job.batch/attachdn-my-release-db1-data1   0/1           10m        10m
job.batch/attachdn-my-release-db1-data2   0/1           10m        10m
job.batch/createdb-my-release-db0         0/1           10m        10m
job.batch/createdb-my-release-db1         0/1           10m        10m

NAME                                   TYPE     DATA   AGE   ROLE
secret/my-release-timescaledb-access   Opaque   1      10m
secret/my-release-timescaledb-data     Opaque   1      10m

NAME                                    ENDPOINTS   AGE   ROLE
endpoints/my-release-timescaledb                    10m
endpoints/my-release-timescaledb-data               10m

NAME                                                                   STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE   ROLE
persistentvolumeclaim/storage-volume-my-release-timescaledb-access-0   Bound    pvc-b672ad15-9157-4c9e-88f0-350c2b6cce9d   5G         RWO            standard       10m
persistentvolumeclaim/storage-volume-my-release-timescaledb-data-0     Bound    pvc-0151bdaa-545f-4413-bf27-fd1422842a59   5G         RWO            standard       10m
persistentvolumeclaim/storage-volume-my-release-timescaledb-data-1     Bound    pvc-bb236c62-031c-48d0-9c80-af3302489085   5G         RWO            standard       10m
persistentvolumeclaim/storage-volume-my-release-timescaledb-data-2     Bound    pvc-d9fe236d-4f23-4953-98ca-74d395843979   5G         RWO            standard       10m

Logs Please provide some details from the logs, see Troubleshooting

➜  timescaledb-multinode git:(master) kubectl logs $(kubectl get pod -o name -l release=$RELEASE,role=master) -c timescaledb
error: expected 'logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER]'.
POD or TYPE/NAME is a required argument for the logs command
See 'kubectl logs -h' for help and examples
➜  timescaledb-multinode git:(master) kubectl logs service/my-release-timescaledb
Defaulted container "timescaledb" out of: timescaledb, initdb (init)
Error from server (BadRequest): container "timescaledb" in pod "my-release-timescaledb-access-0" is waiting to start: PodInitializing
➜  timescaledb-multinode git:(master) kubectl logs pod/my-release-timescaledb-access-0
Defaulted container "timescaledb" out of: timescaledb, initdb (init)
Error from server (BadRequest): container "timescaledb" in pod "my-release-timescaledb-access-0" is waiting to start: PodInitializing
➜  timescaledb-multinode git:(master)

Additional context

Error visible in minikube dashboard:

0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.
Failed to pull image "timescale/timescaledb-ha:pg12-ts2.0.0-p0": rpc error: code = Unknown desc = Error response from daemon: manifest for timescale/timescaledb-ha:pg12-ts2.0.0-p0 not found: manifest unknown: manifest unknown
image
paulfantom commented 2 years ago

Multinode helm chart is deprecated and not supported anymore. If you want to see this chart supported then we are looking for community maintainers - https://github.com/timescale/helm-charts/tree/master/charts/timescaledb-multinode#call-for-maintainers

paulfantom commented 2 years ago

I am closing this issue as TimescaleDB-Multinode helm chart is no longer maintained and deprecated. We are looking for potential community maintainers who could help us in getting that helm chart working again. If you wish to become a maintainer, please contact us on slack.

Keep in mind that TimescaleDB is not and will not be dropping multinode setup. Deprecation is only about helm chart.