You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When cert-manager updates the Ironic certs, the Ironic container has logic to force a restart when RESTART_CONTAINER_CERTIFICATE_UPDATED is specified in the environment (which it is by default in the metal3 chart)
The baremetal-operator pod however lacks similar logic, so when the cert rotation happens, it continues using the old cert and fails to connect to Ironic, requiring a manual pod restart to fix.
We should investigate adding similar logic to the BMO container so that it can correctly restart when the Ironic cert is updated.
The text was updated successfully, but these errors were encountered:
When cert-manager updates the Ironic certs, the Ironic container has logic to force a restart when
RESTART_CONTAINER_CERTIFICATE_UPDATED
is specified in the environment (which it is by default in the metal3 chart)The baremetal-operator pod however lacks similar logic, so when the cert rotation happens, it continues using the old cert and fails to connect to Ironic, requiring a manual pod restart to fix.
We should investigate adding similar logic to the BMO container so that it can correctly restart when the Ironic cert is updated.
The text was updated successfully, but these errors were encountered: