Closed amilstead closed 7 months ago
Thank you for reporting this bug.
Would it be possible for you to test deploying the chart from the following branch https://github.com/OpenNMS/helm-charts/tree/mem/NMS-16365 ?
Thank you for reporting this bug.
Would it be possible for you to test deploying the chart from the following branch https://github.com/OpenNMS/helm-charts/tree/mem/NMS-16365 ?
Hi there, thanks!
That seems to get me past the initial installation, however the workload hangs on init
later, as it seems to expect an external postgres database by default.
When I get some actual time I may try deploying said database. That said, it would be nice if this were something the helm chart could support in terms of a deployment to avoid additional extra resource management overhead.
This issue is resolved in the latest release
Describe the bug
Helm chart installation fails on non-OpenShift clusters.
To Reproduce
Use the quickstart instructions here with a non-OpenShift kubernetes cluster: https://opennms.github.io/helm-charts/horizon/, i.e.
The result is a container spec validation error for the core statefulset container:
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(StatefulSet.spec.template.spec.containers[0].securityContext): unknown field "fsGroup" in io.k8s.api.core.v1.SecurityContext, ValidationError(StatefulSet.spec.template.spec.initContainers[0].securityContext): unknown field "fsGroup" in io.k8s.api.core.v1.SecurityContext]
Expected behavior
Helm install succeeds, rendered "NOTES.txt" is printed to console.
Desktop
Additional context
I would like to evaluate OpenNMS for usage in my network, I am using RKE2 as the kubernetes distro of choice.