Olvid bot-daemon is a bridge that lets you automate interactions with Olvid secure-messaging groups.
Have a look at the documentation for more information on how to use it.
This chart leverages the bjw-s common library so that nearly everything is configured via values.yaml.
helm repo add obeone https://charts.obeone.cloud
helm repo update
# Generate a strong admin key and install the chart
helm install olvid-bot obeone/olvid-bot \
--set secrets.admin-credentials.stringData.OLVID_ADMIN_CLIENT_KEY_CLI="$(openssl rand -hex 24)"
kubectl create secret generic admin-credentials \
--from-literal=OLVID_ADMIN_CLIENT_KEY_CLI=<your-key>
helm install olvid-bot myrepo/olvid-bot-daemon \
--set secrets.admin-credentials.enabled=false
Key | Default | Purpose |
---|---|---|
controllers.main.containers.main.image.tag |
`` | Daemon image tag |
service.main.ports.grpc.port |
50051 |
Internal gRPC port |
persistence.data.size |
1Gi |
PVC size for /daemon/data |
secrets.admin-credentials.enabled |
true |
Whether to create the Secret |
See values.yaml for the full list of options.
kubectl run
)Launch a one-off interactive pod in the same namespace as the daemon:
kubectl run -it --rm olvid-cli \
--image=olvid/bot-python-runner:1.4.1 \
--restart=Never \
--env=OLVID_DAEMON_TARGET=olvid-bot:50051 \
--env=OLVID_ADMIN_CLIENT_KEY=$(kubectl get secret admin-credentials -o jsonpath='{.data.OLVID_ADMIN_CLIENT_KEY_CLI}' | base64 -d) \
--command -- olvid-cli
-it --rm
gives you an interactive shell and removes the pod when you exit.olvid-bot:50051
works because the pod runs in the same namespace as the service.$(kubectl …)
substitution with your own key.helm upgrade olvid-bot obeone/olvid-bot --reuse-values
Bump appVersion
in Chart.yaml to upgrade the daemon image.
helm uninstall olvid-bot
The PVC and Secret are retained by default. Delete them manually if you no longer need them.
Released under the terms of the upstream Olvid project.