-
Notifications
You must be signed in to change notification settings - Fork 181
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
Docs for k8s installs #550
Comments
The docker compose deployment just works. It should be possible to deploy the helm chart without deploying a half k8s cluster. Because almost all users will have already an ingress controller and cert manager etc. |
Thanks for the link. But I still have the problem that there seems to be no way to use an already existing ingress controller and clusterissuer. When enabling the ingress in the helm chart, I get the following error:
|
+1 for the issue. Also have to say this is worst helm chart implementation I have seen. |
Hey @arana198, thanks for your kind comment... You are more than welcome to suggest improvements (you know, we call it open source) ! |
I have created a PR with changes #567 however I need write access which I haven't been granted yet |
thx for submitting @arana198 ! |
Yes I did, twice. |
cool thx |
Hello, How long does it take to get write access after signing the CLA? |
hello |
Hello there, is there a timeframe for this review? |
Where are the docs of the helm values? I have read https://pydio.com/en/docs/cells/v4/kubernetes-quick-install, but I haven't found the docs of the helm values. On https://pydio.com/en/docs/cells/v4/k8s-advanced-parameters only the helm charts which are used as dependencies are documented. For example, how can I change the storage class or the size of the PVCs?
In my opinion, it should not be necessary to use
helm pull
to download the helm chart from the repo and then extract it to see the whole helm values. Is there a GitHub link of the helm chart, which I haven't found?EDIT: it seems impossible to install the helm chart on an already existing k8s cluster. Because the helm chart deploys its own ingress controller and cert manager, with no obvious way to disable this.
The text was updated successfully, but these errors were encountered: