Closed SalmanIsha closed 1 year ago
Hi there,
I do not really have an idea what is going wrong there, as I don't have this problem in any of the deployments I did so far.
What kind of storage backend are you using in your cluster? What Kubernetes Distribution are you using?
Thanks
Christian
Want to share any details? Otherwise I would like to close this issue.
Hi Christian,
Sorry for not getting back to you. Our issue was solved. We had to add a security context in the values.yaml file to get it work. Our storage class was external nfs server.
Kind Regards Mohd Salman Isha
From: Christian Anton @.> Sent: Thursday, November 3, 2022 8:20:43 AM To: zabbix-community/helm-zabbix @.> Cc: Salman Isha @.>; Author @.> Subject: Re: [zabbix-community/helm-zabbix] Permission issue when enabling persistance (Issue #8)
Want to share any details? Otherwise I would like to close this issue.
— Reply to this email directly, view it on GitHubhttps://github.com/zabbix-community/helm-zabbix/issues/8#issuecomment-1301770915, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYX2H7IRT32FWPMHH2PIA3WGNYVXANCNFSM6AAAAAARCQEIBI. You are receiving this because you authored the thread.Message ID: @.***>
I see, that's a common case then and not really specific to this helm chart. Nice to know you were able to solve it. Happy helming and happy Zabbixing :-)
Hello,
I have almost done the bare metal installation of this helm chart except enabling the existing pv claim. And then it breaks my deployment. The postgres pod is getting error like below, I have also disabled the password auto generator:
chown: changing ownership of '/var/lib/postgresql/data/pgdata': Operation not permitted
I am very much confused where I am doing the mistakes. If I add securityContext ( runasuser: 65534) in the values.yaml file the postgres pod works fine but then the zabbix web can't up the nginx service.
Anyone have idea what is going wrong here?