XML

Word

Printable

Type: Epic
Resolution: Duplicate
Priority: Major
Fix Version/s: ACM 2.9.0
Affects Version/s: None
Component/s: Application Lifecycle
Labels:
None

Epic Name:
ACM Options to configure permissions when adding Managed-Clusters into ArgoCD
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Intelligence Requested:
Market:

Epic Goal

...

Currently in the ArgoCD push model, only cluster admin secret on each managed cluster is generated and imported to the ArgoCD server namespace. As a result, ArgoCD users can deploy all kinds of resources to the managed cluster without RBAC control.

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

Previous Work (Optional):

Open questions:

Done Checklist

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 - Downstream documentation merged: <link to meaningful PR>

is related to

ACM-3987 Generate cluster secrets with RBAC SA/User used in ArgoCD push model

Closed

Assignee:: Christian Stark

Reporter:: Christian Stark

QA Contact:: Derek Ho

Architect:: Xiangjing Li

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2023/02/08 4:46 PM

Updated:: 2023/08/02 10:30 AM

Resolved:: 2023/08/02 10:30 AM

Details

Description

Epic Goal

Why is this important?

Scenarios

Acceptance Criteria

Dependencies (internal and external)

Previous Work (Optional):

Open questions:

Done Checklist

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates