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

Add note of temporary Helm chart alpha limitations #5153

Merged
merged 3 commits into from
Mar 7, 2025
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/reference/announcements/880.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,15 @@ Camunda 8.8 introduces a streamlined architecture, consolidating core components

You can download the alpha release of the unified package from the Camunda GitHub repository, either as an executable Java application (Camunda Orchestration Core) or a Docker image.

### Identity and authentication limitations in 8.8.0-alpha2
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've placed this in the section of the Announcements that deals specifically with the Helm chart, but we also have a section on the overall Identity management changes.


The 13.0.0-alpha2 Helm chart released with Camunda 8.8.0-alpha2 establishes a new default setup to support 8.8 [Identity management updates](#identity-management-updates-saasself-managed). Currently, this setup is limited to the following components:

- The Orchestration core (Zeebe, Operate, Tasklist, and Orchestration Identity)
Copy link
Contributor

Choose a reason for hiding this comment

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

Does the "orchestration core" also include Optimize? That's what we have in glossary.md, but wasn't sure with how unique Optimize is.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The slack conversation is here: https://camunda.slack.com/archives/C01H4NG9XDY/p1740070705216559

But I would hold off on any immediate follow-up based on this comment #5133 (comment) - it sounds like Optimize will help take on that discussion.

Copy link
Contributor

Choose a reason for hiding this comment

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

We don't have "Orchestration Identity" elsewhere in the docs -- do we need to newly define this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Part of #5133, so this could be linked if needed once that's merged.

- Connectors

This temporary limitation will be resolved in subsequent alpha releases.

### Helm charts

If you are using the recommended Camunda 8 deployment option ([Helm charts](/self-managed/setup/install.md)), the upgrade path from version 8.7 to 8.8 will be straightforward by changing the values file to the new syntax.
Expand Down
9 changes: 9 additions & 0 deletions docs/self-managed/setup/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,15 @@ sidebar_label: "Install"
description: "Camunda provides continuously improved Helm charts, of which are not cloud provider-specific so you can choose your Kubernetes provider."
---

:::note
The 13.0.0-alpha2 Helm chart released with Camunda 8.8.0-alpha2 establishes a new default setup to support 8.8 [Identity management updates](/docs/reference/announcements/880.md#identity-management-updates-saasself-managed). Currently, this setup is limited to the following components:

- The Orchestration core (Zeebe, Operate, Tasklist, and Orchestration Identity)
- Connectors

This temporary limitation will be resolved in subsequent alpha releases.
:::

We recommend using Kubernetes and Helm to deploy and run Camunda 8 Self-Managed in production.

There are many ways you can provision and configure a Kubernetes cluster, and there are a number of architectural choices you need to make. Will your workers run in the Kubernetes cluster or external to it? You will need to configure your Kubernetes cluster and modify this to suit the architecture you are building.
Expand Down
Loading