Feature Overview

Goals

As of this writing, when Argo CD communicates with Argo CD agent, and when Argo CD agent communicates with redis, that communication is over a plaintext (non-TLS connection)

Use of plaintext in this case enables the possibility of eavesdropping (or even malicious modifications) of redis traffic.

• Granted, an internal K8s cluster would generally be considered to be (at least partly) trusted, but this is about defense in depth.

Since redis traffic often contains important data (credentials), it is beneficial to enable TLS on redis.

Requirements

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