Feature Overview

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.

Goals

<Who benefits from this feature, and how? What is the difference between today's current state and a world with this feature?>

Requirements

Use Cases

<What are we making, for who, and why/what problem are we solving?>

Out of scope

<Defines what is not included in this story>

Dependencies

<Link or at least explain any known dependencies.>

Background, and strategic fit

<What does the person writing code, testing, documenting need to know?>

Assumptions

<Are there assumptions being made regarding prerequisites and dependencies?>

<Are there assumptions about hardware, software or people resources?>

Customer Considerations

<Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation/QE Considerations

<What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?>

<Does this feature have a doc impact? Possible values are: New Content, Updates to existing content,  Release Note, or No Doc Impact?>

<Are there assumptions being made regarding prerequisites and dependencies?>

<Are there assumptions about hardware, software or people resources?>

Impact

<If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

<links>

Definition of Ready

• The objectives of the feature are clearly defined and aligned with the business strategy.
• All feature requirements have been clearly defined by Product Owners.
• The feature has been broken down into epics.
• The feature has been stack ranked.
• Definition of the business outcome is in the Outcome Jira (which must have a parent Jira).

• …