Helm install not working with both helm and deployment.yaml #457
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The k8s version used here:
Client Version: v1.27.2
Kustomize Version: v5.0.1
Server Version: v1.27.2
When installing gitea with
helm install gitea-charts/gitea -n gitea
, without a values.yaml file, the installation fails:When done with
helm install -f values.yaml gitea-charts/gitea -n gitea
where a persistent volume is set:values.yaml:
values2.yaml (this failed with the same errors)
Furthermore, there was an issue when attempting to deploy gitea using a deployment.yaml. Behind this is an ingress that exposes it to the internet - the ingress also exposes other services and is working.
This method failed after the "Install gitea" button on the initial setup. It would load (staying on the setup page, not showing the cup animation) for 1-2 minutes before ending in an 504 Error.
deployment.yaml > i've tried different values for mountPath, none of them lead farther then mentioned above.
Error given by
kubectl logs -f gitea-XXXXXXXX-XXXXX - gitea
If need be or if it's more convenient, you can reach me over Discord (this issue was made after being advised so by techknowlogick)
There are issues with your PVC creation that you need to debug yourself -> describe your PVC and see what the issue is. It's most likely not a chart issue as many others successfully use this chart including a PVC spawned from it. In either case, logs are preferred over screenshots :)
Gitea is currently using a statefulset within the chart. There is no need for a manual deployment on the side - I don't understand what you want to achieve. Helm charts are fully packaged installation recipes without the need for additional components. We can't help you if you go off-road :)
You always want a values file as there are certain settings you must / should change for a functional deployment. But again I don't think that the lack of the values file is the issue here as you also get the same PVC error with it.
Stale -> closing, feel free to re-open if needed.