Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [x] Mandatory: Add the required version to the Fix version/s field.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [ ] We need to update to an existing topic

• [ ] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [x] We need a z-Stream (Errata) Advisory and Release note for
  MCE and/or ACM

3. - [x] Mandatory: Find the link to where the documentation update
should go and add it to the recommended changes. You can either use the
published doc or the staged repo for this step:

Note: As the feature and doc is understood, this recommendation may
change. If this is new documentation, link to the section where you think
it should be placed.

Customer Portal published version

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12

Doc staged repo within the ACM Workspace:
https://github.com/stolostron/rhacm-docs

4. - [x] Mandatory for GA content:

• [ ] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:

• [ ] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

• [ ] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)

• [ ] Add link to dev story here:

5. - [x] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.

-------------------------------------------------------------------

Link to advisory: https://gitlab.cee.redhat.com/acm/acm-release-management/-/merge_requests/5

-------------------------------------------------------------------

Some context first:

MCE 2.9.0 will be the first MCE release with Konflux. Prior to that only one release and therefore one advisory was emitted
example: https://access.redhat.com/errata/RHBA-2025:8527
other example for what I understand is MCE 2.8.0: https://errata.devel.redhat.com/advisory/details/139934 

Now with Konflux, a limitation forces us to release assisted-installer components separately. They will have their own advisory. And because of a second limitation, from prodsec, rhel8 images will have their own advisory & rhel9 images will have their own advisory.

What is the ask:

Can you help us write the content for the following fields of those 2 advisories ?

• Synopsys
• Topic
• Problem description
• Solution

Since those images are dedicated to MCE release, we want to make it clear it's for MCE 2.9.0. We also want to make it clear that is the advisory just for assisted-installer components and for rhel8/9

Proposal:

• Reuse as much as possible https://errata.devel.redhat.com/advisory/details/139934
• Add a small sentence to make it clear it's bound to assisted-installer components & rhel8/9
• Update the documentation link to point to the doc for assisted-installer for MCE (lgamliel did you have something specific in mind ?)
• Can you validate that the doc link is still valid for 2.14 ? I copy paste the one from 2.13 but 2.14 is not released yet (obviously)

Synopsys

Assisted Installer RHEL 9 components for multicluster engine for Kubernetes 2.9.0

Topic

Assisted Installer RHEL 9 components for the multicluster engine for Kubernetes 2.9.0 General Availability release

Problem Description

Assisted Installer RHEL 9 integrates components for the general multicluster engine for Kubernetes 2.9.0 release (why?).

The multicluster engine for Kubernetes provides the foundational components that are necessary for the centralized management of multiple Kubernetes-based clusters across data centers, public clouds, and private
clouds.

You can use the engine to create new Red Hat OpenShift Container Platform clusters, or to import existing Kubernetes-based clusters for management.

After the clusters are managed, you can use the APIs that are provided by the engine to distribute configuration based on placement policy.

Solution

For more information about Assisted Installer, see (link to https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/clusters/cluster_mce_overview#cim-intro )

For multicluster engine for Kubernetes, see the following documentation for
details on how to install the images:

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/clusters/cluster_mce_overview#mce-install-intro

This documentation will be available after the general availability release of Red Hat Advanced Cluster Management 2.14.

cc lgamliel alkaplan@redhat.com