Add note of temporary Helm chart alpha limitations #5153
Conversation
|
👋 🤖 🤔 Hello, @conceptualshark! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
conceptualshark
added
8.8.0-alpha2
component:docs
conceptualshark
changed the title
There was a problem hiding this comment.
I think calling out this limitation in the Helm install page and Announcements makes the most sense, but am open to other options. We could probably link out to additional support info once #5133 is finished.
| @@ -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 | |||
There was a problem hiding this comment.
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.
docs/reference/announcements/880.md
Outdated
|
|
||
| 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) |
There was a problem hiding this comment.
Does the "orchestration core" also include Optimize? That's what we have in glossary.md, but wasn't sure with how unique Optimize is.
There was a problem hiding this comment.
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.
docs/reference/announcements/880.md
Outdated
|
|
||
| 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) |
There was a problem hiding this comment.
We don't have "Orchestration Identity" elsewhere in the docs -- do we need to newly define this?
There was a problem hiding this comment.
Part of #5133, so this could be linked if needed once that's merged.
Description
Resolves https://github.com/camunda/documentation-team/issues/464
The release of 8.8.0-alpha2 delivers Orchestration-level Identity with basic authentication capabilities limited to select components. A note has been added to both the Helm installation docs and the 8.8 Announcements to ensure there is notification of this change for any alpha users.
#5154 - this issue has been created to ensure this limitation notice is removed in the next release.
When should this change go live?
bugorsupportlabel)available & undocumentedlabel)holdlabel)low priolabel)PR Checklist
/docsdirectory (version 8.8)./versioned_docs/version-8.7/directory (version 8.7)./versioned_docsdirectory.@camunda/tech-writersunless working with an embedded writer.