Epic Goal

Enable Pod Log Streaming in Agent Architecture. Users should be able to view pod logs from workload clusters on the control plane.

Refer Enable Pod Log Streaming in Agent Architecture proposal for implementation details.

Why is this important?

A very popular feature in Argo CD is the ability to view the logs of pods from the Argo CD UI, regardless of where the pod is being run. Similar to the runnable actions, streaming the logs require access from the Argo CD API server to the managed cluster’s API, which is not possible with argocd-agent’s architecture.

We need to think about a way to implement log streaming in a decoupled way, for example a gRPC stream between managed cluster and control plane that can then be consumed by the Argo CD API server, and thus exposed via the Argo CD UI.

Scenarios

1. ...

Other Considerations

• <Call out anything explicitly as Out of Scope?>
• <Call out internal and external dependencies?>
• <Are there any known previous works?>
• <Any unanswered questions?>

Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

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