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
[BUG] Kubernetes deployment doesn't consume config.yaml #244
Comments
I seem to have been able to fix this by looking back at previous versions of the deployment yaml and reintroducing the config volume:
was this meant to be removed? |
Have same issue. Playing around with volumes and what not can get it working again but as it is, it does not work. |
Unfortunately, we don't have the bandwidth to debug the Kubernetes deployment. We would most certainly appreciate a contribution if you happen to fix this. |
Would a pull request with a working manifest suffice? If so I can get provide one after the holiday season. |
For me, in the Kubernetes, it worked with the following: For Docker Swarm, I've done the following: |
Hey @hipnologo , can you please supply your code for Docker Swarm? |
Describe the bug
Modifying values in config.yaml such as enabling auth or disabling summarizing does not affect the Zep server.
To Reproduce
Modify some values in config.yaml:
create configmap with:
kubectl create configmap zep-config --from-file=config.yaml -n zep
Deploy with:
kubectl apply -f zep-k8-deployment.yaml.
(Reboot deployment if already running)
The JSON printout in the web GUI is unchanged, and
Expected behavior
Zep will now require an API key and summarization will be disabled.
Logs
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: