Atmosphere-Operator CrashLoopBackOff issue about atmosphere HOT 4 CLOSED

@runlevel-six we should be able to do that moving forward, but I think we hadn't gotten around going back to the existing tools.

I'll try to find sometime to flip all of the components to be configurable

from atmosphere.

@runlevel-six the logs are not great, but I think the issue here is that the helm release never transitioned to applied.

can you check all the helm releases and see if one is failed?

kubectl get helmrelease --all-namespaces

from atmosphere.

@mnaser you are right. I didn't realize that node-feature-discovery had been pulled into the operator - we deploy that separately so I suspect that is why the HelmRelease is failing.

Just curious, in the same manner that you did ingress-nginx, would it be feasible to make any of the non-OpenStack components installed by the operator flagged to be skipped (or with overrides if we use it but have a different configuration)?

from atmosphere.

Closing since the answer was determined, and #159 opened with a request for the new feature that would resolve this.

from atmosphere.