Camunda 8.6 is undergoing a major architectural update that will impact deployment methodology. When 8.6 is released, our Customer must be able to upgrade all their environments (dev, test, prod) and get a continuity of service.
As an IT Admin, I can upgrade Camunda 8.5 in my K8s cluster to 8.6 without any upgrade issues
As an IT Admin, I can follow a clear upgrade guide that I can use to plan my migration.
The guide includes the 8.6 deployment architecture so that our users know how to deploy the new 8.6 architecture to K8s. (even if changes are minimal, we must clarify our message on how architecture change impacts deployment.)
We will define standard 8.5 deployment architectures that will be validated with the upgrade process.
We will document non-Helm use cases and will highlight configuration changes that are automated by HELM.
Implementation Notes
Considering a change to the architecture in 8.6, we pre-suppose a high-risk update process.
Customers need to know how new Architecture impacts deployment for 8.5 deployments to lower risk assessment for our customers.
8.6 upgrade guide will be based on a recommended, standard 8.5 deployment blueprint.
Following the upgrade to 8.6, the final deployment should align with one of the recommended 8.6 blueprints. However, we expect real-life infrastructure to cause our customers to deviate from this architecture.
We will make available as Alphas and RC candidates for internal stakeholders and early Customer\/Partner adopters.
We will take into account non-Helm use cases (Known customer that do not use K8s and HElm) and will document configuration changes that HELM is automating so that customers can replicate in their own environments
:robot: This issue is automatically synced from: source
Value Proposition Statement
Camunda 8.6 is undergoing a major architectural update that will impact deployment methodology. When 8.6 is released, our Customer must be able to upgrade all their environments (dev, test, prod) and get a continuity of service.
User Problem
Users need to upgrade from 8.5 to 8.6
--> See summary of changes coming with 8.6
Release Notes
User Stories
As an IT Admin, I can upgrade Camunda 8.5 in my K8s cluster to 8.6 without any upgrade issues
As an IT Admin, I can follow a clear upgrade guide that I can use to plan my migration.
The guide includes the 8.6 deployment architecture so that our users know how to deploy the new 8.6 architecture to K8s. (even if changes are minimal, we must clarify our message on how architecture change impacts deployment.)
We will define standard 8.5 deployment architectures that will be validated with the upgrade process.
We will document non-Helm use cases and will highlight configuration changes that are automated by HELM.
Implementation Notes
Considering a change to the architecture in 8.6, we pre-suppose a high-risk update process.
Customers need to know how new Architecture impacts deployment for 8.5 deployments to lower risk assessment for our customers.
8.6 upgrade guide will be based on a recommended, standard 8.5 deployment blueprint.
Following the upgrade to 8.6, the final deployment should align with one of the recommended 8.6 blueprints. However, we expect real-life infrastructure to cause our customers to deviate from this architecture.
We will make available as Alphas and RC candidates for internal stakeholders and early Customer\/Partner adopters.
We will take into account non-Helm use cases (Known customer that do not use K8s and HElm) and will document configuration changes that HELM is automating so that customers can replicate in their own environments
:robot: This issue is automatically synced from: source