Epic Goal

Let us assume you deploy an Application to a cluster and have clusterreplicas 1.
The cluster goes down and the Application is moved to another cluster.

The placementdecision gets reevaluated and there should be an option to handle it.

Customer was asking e.g. to use a Script and setup some netapp specific configuration on the new cluster which is selected.

The process must be:

• stable
• rebust
• easy to configure

.

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

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 - 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.