Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

release: disable atomic flag for initial install #256

Merged
merged 1 commit into from
Jan 29, 2020

Conversation

hiddeco
Copy link
Member

@hiddeco hiddeco commented Jan 29, 2020

As it does not play nicely with some bootstrapping scenarios, enabling the (waiting) behaviour is still possible by setting .spec.wait to true.

Fixes #255

As it does not play nicely with some bootstrapping scenarios,
enabling the (waiting) behaviour is still possible by setting
`.spec.wait` to `true`.
@hiddeco hiddeco requested a review from stefanprodan January 29, 2020 10:01
Copy link
Member

@stefanprodan stefanprodan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hiddeco hiddeco merged commit f31bd47 into master Jan 29, 2020
@hiddeco hiddeco deleted the enhancement/do-not-set-atomic branch January 29, 2020 13:25
@marshallford
Copy link

Would it be reasonable to set .spec.wait to true by default to prevent a breaking change?

@hiddeco
Copy link
Member Author

hiddeco commented Feb 13, 2020

@marshallford no, as the behaviour should not have been introduced to start with and the breaking change being made was actually using the --atomic flag (see linked issue).

@marshallford
Copy link

I guess there was two breaking changes then, because I was relying on the --atomic being present by default.

@hiddeco
Copy link
Member Author

hiddeco commented Feb 13, 2020

It depends on the moment you started using the operator, but note that:

  1. part of the --atomic behaviour is still present (as a failed installation still results in the removal of the release)
  2. the atomic behaviour only happened on chart installations, given those are already installed in your cluster, this change should have no effect on those existing releases

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add property to disable atomic installation
3 participants