Loading...

XML

Word

Printable

Epic Name:
Agent User Documentation Architecture/concepts
Size:
S
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Status:
To Do
Feature Link:
SECFLOWOTL-275 - Multi-cluster GitOps: User documentation
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Release Note Text:

Hide
Argo CD Agent-based architecture is now GA::

With this update, the Argo CD Agent functionality in GitOps Operator is promoted from Technology Preview (TP) to General Availability (GA). This feature enables Argo CD to use a agent-based, pull-based approach to Argo CD Application deployment, which leads to improved scalability, security, reliability, and more. Learn more about the Argo CD agent functionality at (doc link to argo cd agent architecture page)

Show
Argo CD Agent-based architecture is now GA:: With this update, the Argo CD Agent functionality in GitOps Operator is promoted from Technology Preview (TP) to General Availability (GA). This feature enables Argo CD to use a agent-based, pull-based approach to Argo CD Application deployment, which leads to improved scalability, security, reliability, and more. Learn more about the Argo CD agent functionality at (doc link to argo cd agent architecture page)
Release Note Type:
Feature
Intelligence Requested:
Market:

Epic Goal

Produce product documentaion on Argo CD Agent for users
Topic should cover:
- General concepts and differences to classical GitOps are documented
- Argo CD Agent concept and architecture
- Brief overview about agent modes are documented

Code Complete:
- All code has been written, reviewed, and approved.
Tested:
- Unit tests have been written and passed.
- Integration tests have been completed.
- System tests have been conducted, and all critical bugs have been fixed.
- Tested on OpenShift either upstream or downstream on a local build.
Documentation:
- User documentation or release notes have been written.
Build:
- Code has been successfully built and integrated into the main repository / project.
Review:
- Code has been peer-reviewed and meets coding standards.
- All acceptance criteria defined in the user story have been met.
- Tested by reviewer on OpenShift.
Deployment:
- The feature has been deployed on OpenShift cluster for testing.
Acceptance:
- Product Manager or stakeholder has reviewed and accepted the work.