Closed russellb closed 5 years ago
There isn't currently a configuration option for this, because we didn't think we were going to need one.
Yeah, I was thinking that we need a workaround until ironic is running in the baremetal-operator pod
workaround here: https://github.com/metalkube/baremetal-operator/pull/127
When we deploy the baremetal-operator using dev-scripts, it needs to be configured to talk to Ironic on the provisioning host until we have the baremetal-operator updated to run Ironic itself inside the cluster.
Right now it assumes it can reach Ironic on localhost, which fails when running the BMO as a pod.