You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Istio configured to inject sidecars in containers for the namespace that contains the database and seaweedfs (same namespace), the wait-for-db init container within the seaweedfs-filer pod does not complete.
Failed with Istio 1.22.3
The postgresql database is installed using the bitnami postgresql chart and is fully running in advance and has the Istio sidecar attached.
The seaweedfs-filer has the wait-for-db pod continuing to fail to connect since the istio-proxy (sidecar) is not yet running. It is in PodInitializing. I expect it will remain in this state until the wait-for-db init container completes.
Are you using any custom parameters or values?
Using external database settings to connect to a Postgres that is installed first with the seaweedfs table definition.
What is the expected behavior?
seaweedfs-filer pod's wait-for-db is able to connect to postgresql and then the pod fully comes up.
What do you see instead?
wait-for-db remains in 'Waiting' stage within Kubernetes and then ultimately restarts.
Log for wait-for-db: postgresql 14:54:34.49 INFO ==> Waiting for host seaweedfs-postgres-postgresql.<truncated> 2025-01-02T14:55:34.651244546Z postgresql 14:55:34.65 ERROR ==> Database not ready
Additional information
The same chart versions/configuration without Istio works properly and seaweedfs fully comes up.
Tested from a clean Helm install in both positive and negative configurations described.
The text was updated successfully, but these errors were encountered:
Thank you for bringing this issue to our attention. Unfortunately, Istio is not supported out of the box. While some Helm charts have received community contributions to work with Istio, this is not a general feature across the catalog.
If you're interested in contributing a solution, we’d love to see your pull request! The Bitnami team is eager to review your submission and provide feedback. You can find the contributing guidelines here.
Your contribution would be a valuable addition to the community. Feel free to reach out if you have any questions or need assistance during the process.
Name and Version
bitnami/seaweedfs 4.2.0
What architecture are you using?
amd64
What steps will reproduce the bug?
With Istio configured to inject sidecars in containers for the namespace that contains the database and seaweedfs (same namespace), the wait-for-db init container within the seaweedfs-filer pod does not complete.
Failed with Istio 1.22.3
The postgresql database is installed using the bitnami postgresql chart and is fully running in advance and has the Istio sidecar attached.
The seaweedfs-filer has the wait-for-db pod continuing to fail to connect since the istio-proxy (sidecar) is not yet running. It is in PodInitializing. I expect it will remain in this state until the wait-for-db init container completes.
Are you using any custom parameters or values?
Using external database settings to connect to a Postgres that is installed first with the seaweedfs table definition.
What is the expected behavior?
seaweedfs-filer pod's wait-for-db is able to connect to postgresql and then the pod fully comes up.
What do you see instead?
wait-for-db remains in 'Waiting' stage within Kubernetes and then ultimately restarts.
Log for wait-for-db:
postgresql 14:54:34.49 INFO ==> Waiting for host seaweedfs-postgres-postgresql.<truncated> 2025-01-02T14:55:34.651244546Z postgresql 14:55:34.65 ERROR ==> Database not ready
Additional information
The same chart versions/configuration without Istio works properly and seaweedfs fully comes up.
Tested from a clean Helm install in both positive and negative configurations described.
The text was updated successfully, but these errors were encountered: