refactor(api): changing rollingUpdate default to true #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #81
Description
Druid requires a rolling update in order to apply changes with no downtime. The operator supports it with the
rollingUpdate
field.Currently, this behavior is disabled by default for no reason.
This PR changes Druid's API
rollingUpdate
field to betrue
by default. This is done by using a Kubebuilder marker.This PR has:
Key changed/added files in this PR
apis/druid/v1alpha1/druid_types.go