-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Argo Agent: Delivery mechanism using manifests
-
False
-
None
-
False
-
SECFLOWOTL-154 - Argo Agent: Delivery mechanism using manifests
-
0% To Do, 0% In Progress, 100% Done
-
-
Epic Goal
- The agent needs to be deployable on OpenShift clusters. For this reason, we will need a set of manifests (plain or Kustomize) to deploy the agent workload and the principal component on the cluster. Furthermore, documentation need to exist on how to install the agent components and any pre-requisite.
Why is this important?
- …
Scenarios
- ...
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment