Story (Required)

As a <PERSONA> trying to <ACTION> I want <THIS OUTCOME>

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

List of kuttl tests failed on operator-redesign branch 

1-0017_validate_cmp (731.22s)
1-021_validate_notification_controller (347.17s)
1-034_validate_applicationset_reconcile_enabled_set_false (8.73s)
1-032_validate_dynamic_scaling (8.81s)
1-024_validate_apps_in_any_namespace (18.81s)
1-016_validate_keycloak (189.41s)
1-014_validate_parallelism_limit (75.50s)
1-009_validate_log_level_format (43.27s)
1-002_validate_cluster_config (311.40s)
1-001_validate_basic (48.36s)

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met