-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Test Hook to be turned off #77
Comments
How and exactly with which command(s) and flags are you installing the chart? Normally, the test should only be deployed and run when executing |
I started looking into that after creating this, we use Harness to deploy, and i believe it is automatically running the test hook on a rolling deploy. So not entirely something this chart is doing, but I do appreciate the small enhancement for the tests working without a download EDIT: Yes, it seems that when Harness does a Helm deploy, it's expanding all files under the |
This also improves the integration test runtime and reliability by not installing a fresh cluster for every test but upgrading it with the new config. Fixes #77
* Fix probes when Qdrant is served over TLS This also improves the integration test runtime and reliability by not installing a fresh cluster for every test but upgrading it with the new config. Fixes #77 * Deactivate liveness and startup probes by default Since these probes restart the pod on failure, they can disrupt the health of the Qdrant cluster unnecessarily and cause more problems then actually help. Having a readinessProbe is usually enough. * Fix tests * Try to fix connection issues
When running a helm install from behind an Enterprise Proxy and Firewall, the Test hook continually fails due to firewall blocking the python 3.11 download being done in the test script.
I would like to be able to toggle off the Test Hook to stop the test pod from being spun up at all, as it is always in 'Error' state after a deploy, requiring manual intervention to delete and remove.
When I don't remove the failed pod and attempt to helm install again, I get this error:
Test-DB-Interaction Container Startup Error
Error:
The text was updated successfully, but these errors were encountered: