-
Notifications
You must be signed in to change notification settings - Fork 15
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
linkding 1.0.5 Helm chart broke my deployment #298
Comments
Hi @kalmarz, Thanks for reporting this! You're right, there are two bugs in the Helm Chart. 🙈 BR, Pascal |
Please see the latest release |
It did. Thank you for the prompt update. |
@all-contributors please add @kalmarz for bug 👌🏻 |
I've put up a pull request to add @kalmarz! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to upgrade from chart version
0.3.1
to the latest1.0.5
(at the time of writing) and it failed with the error:reconciliation failed: Helm upgrade failed: cannot patch "linkding" with kind Deployment: Deployment.apps "linkding" is invalid: spec.template.spec.containers[0].volumeMounts[0].name: Not found: "storage-volume"
I have a pre-baked PV and PVC that I refer to and they've worked quite well so far.
The cluster is managed with FluxCD, hence the
HelmRepository
andHelmRelease
objects. What I saw among the k8s events was the Helm release tried to provision another volume, namedlinkding-storage
and disregarded my pre-made PV and PVC although they were there and named exactly as the release required. Any pointer would be greatly appreciated.The text was updated successfully, but these errors were encountered: