Any insights into why the helm install fails?
helm install alfresco-incubator/alfresco-content-services-community --generate-name --set repository.adminPassword="17cd2fxxxxxxxxxxxxxxxxx --set postgresql.postgresPassword=MyDbPwd
fails with the error
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(Deployment.spec.template.spec.containers[0].livenessProbe): unknown field "limits" in io.k8s.api.core.v1.Probe, ValidationError(Deployment.spec.template.spec.containers[0].livenessProbe): unknown field "requests" in io.k8s.api.core.v1.Probe]
Solved! Go to Solution.
I have run into similar issues a couple of weeks ago and I assume this is due to incompatibilities of the chart with the newest version of Helm (3.x) which is only out and about since November of last years, or even more recent Kubernetes releases. I am currently trying to see what (minimal) changes are all necessary to make this work and potentially create a PR for the Alfresco deployment project. You may find it simpler to just downgrade to Helm 2.x and/or an older Kubernetes version at this time.
I have run into similar issues a couple of weeks ago and I assume this is due to incompatibilities of the chart with the newest version of Helm (3.x) which is only out and about since November of last years, or even more recent Kubernetes releases. I am currently trying to see what (minimal) changes are all necessary to make this work and potentially create a PR for the Alfresco deployment project. You may find it simpler to just downgrade to Helm 2.x and/or an older Kubernetes version at this time.
Thank you very much for your reply. Is there a bug created already fro this?
I don't know how much https://github.com/Alfresco/acs-community-deployment/issues/93 relates to this - it definitely is a different error message, but that issue has also been around a couple months more than I am aware of the problem. Helm 3 was not out at the time, and so the constellation was a bit different, but the underlying cause might be the same.
Is there a resolution on this issue ? We are getting the same error when deploying ACS using Heml 3.0 on K8 v1.17. Does downgrading helm to v2.0 resolves this issue ? is there a newer version of the helm chart that fixes this issue ?
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.