Skip to content
This repository was archived by the owner on Nov 26, 2025. It is now read-only.

Conversation

@Kidswiss
Copy link

Previously, setting tika.enabled: false broke the opencloud deployment because the env vars are hard-coded into the deployment.

If the Tika service is not available during the startup of the opencloud deployment, then it will simply crashloop.

Previously, setting `tika.enabled: false` broke the opencloud deployment
because the env vars are hard-coded into the deployment.

If the Tika service is not available during the startup of the opencloud
deployment, then it will simply crashloop.
@Tim-herbie
Copy link
Contributor

Hi @Kidswiss,
did you test it already that opencloud works when you didn´t set the ENV?

@Kidswiss
Copy link
Author

I currently have it running without the env vars:

16:25:00 in ~ via 🐳 orbstack at ☸️ default
➜ k -n opencloud get pods opencloud-opencloud-69f6869f79-xnkst -oyaml | grep SEARCH

16:25:14 in ~ via 🐳 orbstack at ☸️ default
➜ 1 k -n opencloud get pods
NAME                                   READY   STATUS    RESTARTS   AGE
opencloud-opencloud-69f6869f79-xnkst   1/1     Running   0          2d21h

Copy link
Contributor

@Tim-herbie Tim-herbie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants