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 enabling or disabling HA for a service on a running Spinnaker, Halyard will not clean up the old service(s) by default. This means that if a non-HA Clouddriver is running (for example) and Spinnaker is then deployed with HA Clouddriver enabled, the non-HA Clouddriver will still be running, even though it is no longer used. To clean up these orphaned services, add a --delete-orphaned-services flag to hal deploy apply as stated here.
I've searched the documentation, but I haven't found the above flag/option in the Spinnaker operator configuration.
Is there a way to achieve the same behavior through the Operator?
The text was updated successfully, but these errors were encountered:
Operator still runs halyard under the hood! I haven't tested this particular flag but it should be possible to exec into the halyard container and run hal deploy apply --delete-orphaned-services from there
When enabling or disabling HA for a service on a running Spinnaker, Halyard will not clean up the old service(s) by default. This means that if a non-HA Clouddriver is running (for example) and Spinnaker is then deployed with HA Clouddriver enabled, the non-HA Clouddriver will still be running, even though it is no longer used. To clean up these orphaned services, add a
--delete-orphaned-services
flag tohal deploy apply
as stated here.I've searched the documentation, but I haven't found the above flag/option in the Spinnaker operator configuration.
Is there a way to achieve the same behavior through the Operator?
The text was updated successfully, but these errors were encountered: