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

[ENHANCEMENT] Deprecate failover / failback mode in 8.6 and complete removal in 8.7 #2286

Closed
Langleu opened this issue Sep 2, 2024 · 6 comments
Assignees
Labels
code-freeze Issue eligible for work during the code freeze kind/enhancement New feature or request lifecycle/deprecation Issues and PRs related to features and components deprecation version/8.6 Camunda applications/cycle version version/8.7 Camunda applications/cycle version

Comments

@Langleu
Copy link
Member

Langleu commented Sep 2, 2024

Describe the use case:

related to Epic: https://github.com/camunda/product-hub/issues/2173

Zeebe introduced in 8.6 a simplification of the failover and failback process. Resulting in a quicker, better, less error prone procedure in 8.6.
This results in failover and failback behaviour of the Helm chart to be obsolete. Therefore, we should remove those options global.multiregion.installationType as we should actively promote the easier new procedure.

For 8.6 the idea was to deprecate it and for 8.7 to fully remove it, giving customers a short period to get accustomed to the new procedure while still providing the old procedure during the deprecation period.

The docs were already updated as part of https://github.com/camunda/team-infrastructure-experience/issues/325 and will be visible with the next docs update.

Reason for deprecating and removing:

  • Only promote simplified and less error-prone procedure
  • longterm, less custom stuff to maintain

Describe the enhancement/feature:

  • global.multiregion.installationType option with related failover / failback code is deprecated in 8.6
  • global.multiregion.installationType option with related failover / failback code is removed in 8.7

Desired outcome and acceptance tests:

  • 8.6 the value / flags are deprecated
    • implementation details and up to you on what's possible
  • 8.7 the value / flags are removed
@Langleu Langleu added kind/enhancement New feature or request version/8.6 Camunda applications/cycle version lifecycle/deprecation Issues and PRs related to features and components deprecation version/8.7 Camunda applications/cycle version labels Sep 2, 2024
@Langleu
Copy link
Member Author

Langleu commented Sep 9, 2024

@aabouzaid is this something Distribution could do for the 8.6 release and later for 8.7?

Not sure what Helm gives as possibility but as said, worst case a statement in the release notes of the Helm chart would be sufficient before finally removed in 8.7.

@aabouzaid
Copy link
Member

@Langleu As Helm doesn't support warning messages but only fail messages, we will add it to the NOTES.txt and official docs.

@jessesimpson36
Copy link
Contributor

jessesimpson36 commented Sep 25, 2024

The notes / docs are both merged. Lets create a follow-up ticket for 8.7 to make sure this option gets removed from the default values.yaml and templates. Then this ticket may be closed

@jessesimpson36
Copy link
Contributor

Follow up ticket to be completed by 8.7
#2380

@jessesimpson36
Copy link
Contributor

Closing this epic since deprecation work is done, and we have the new github issue #2380 which will take care of actually removing this.

@Langleu
Copy link
Member Author

Langleu commented Sep 26, 2024

Thanks @jessesimpson36 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-freeze Issue eligible for work during the code freeze kind/enhancement New feature or request lifecycle/deprecation Issues and PRs related to features and components deprecation version/8.6 Camunda applications/cycle version version/8.7 Camunda applications/cycle version
Projects
None yet
Development

No branches or pull requests

3 participants