Feature Overview

Provide sync abilities for configuration and secrets across principal and agents.

Goals

The agents/principal construct requires some pieces of configuration on the managed systems, as well as managing secrets, such as credentials and certificates.

For example, the agents need credentials. These must be generated on the control plane, and then distributed to the respective agent. We also need ways to revoke credentials on the control plane. Similarly, the agents communicate to the principal using TLS, so we need a central authority that is known to the agents.

These processes need to be automated and secure, and best if centrally managed.

Requirements

Use Cases

• As an administrator, I want to roll out new configuration - such as a new TLS root CA - to all of my agents, or a subset of my agents.
• As an administrator, I want to roll out new secrets - such as new TLS client certificates and keys - to all of my agents, or a subset of my agents

Out of scope

• Generation of config or secrets is out of scope
•  

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

• …