XML

Word

Printable

Type: Epic
Resolution: Done
Priority: Critical
Fix Version/s: ACM 2.8.0
Affects Version/s: None
Component/s: Application Lifecycle, QE
Labels:

Epic Name:
ACM Provide default experience when creating ApplicationSets
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Green
Epic Status:
To Do
Feature Link:
ACM-1551 - ACM Investigating Advanced ApplicationSet Usecases
Parent Link:
ACM-1551ACM Investigating Advanced ApplicationSet Usecases
Hierarchy Progress Bar:

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

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

Intelligence Requested:
Market:

Epic Goal

...When you create ApplicationSets there are currently some steps necessary which are clearly documented but not the perfect onboarding experience.

in ACM 2.6 we have a Global-Clusterset where we could bind a namespace to and deploy ApplicationSets ootb.

Alternatively we could allow creating a GitopsCluster resource from the UI

Why is this important?

... improve default experience

Scenarios

... customer can create an ApplicationSet into a few minutes without previous experience

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-4483 ACM When creating several GitopsClusterResources in a namespace display name and namespace

Closed

ACM-5019 ACM Document new (enhanded, easier) flow for ApplicationSets

Closed

ACM-5189 All referenced cluster sets specified by argo server do not show correctly when there are multiple argo servers

Closed

ACM-5271 ArgoCD server namespace does not show up on RBAC role

Closed

Assignee:: Maggie Chen

Reporter:: Christian Stark

QA Contact:: Ishmam Amin

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

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

Updated:: 2023/05/05 1:10 PM

Resolved:: 2023/05/05 1:10 PM

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