Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleting orphaned services support #218

Open
man0s opened this issue Mar 9, 2021 · 2 comments
Open

Deleting orphaned services support #218

man0s opened this issue Mar 9, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@man0s
Copy link

man0s commented Mar 9, 2021

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?

@sh4sh
Copy link

sh4sh commented May 11, 2021

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

@dogonthehorizon dogonthehorizon added the enhancement New feature or request label Apr 27, 2023
@dogonthehorizon
Copy link
Contributor

Going to mark this as an enhancement as this would be a good thing to do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants