XML

Word

Printable

Epic Name:
A short-term solution to handle errors when "managed cluster CA updates"
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Green
Epic Status:
To Do
Feature Link:
ACM-2320 - Automatically update the hub cluster when certificates are changed on a managed cluster
Parent Link:
ACM-2320Automatically update the hub cluster when certificates are changed on a managed cluster
Hierarchy Progress Bar:

50% To Do, 0% In Progress, 50% Done

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

This Epic aims to:

Warn users via UI when admin kubeconfig becomes invalid (including errors caused by managed cluster CA changes)
Enable users to operate admin kubeconfigs in batch
Allow users to add additional CA or use customized CA when creating/registering a cluster (a GitOps-friendly way to add CA)

In summary, this epic provides a short-term solution for users who want to effectively manage managed cluster CA changes.

Why is this important?

...

...

...

CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.