Goal Summary:

An elevator pitch (value statement) that describes the Feature in a clear, concise way. Complete during New status.

All ACS services should support hot reloading of mTLS certificates (both leaf certificates and the internal CA certificate).

Goals and expected user outcomes:

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

ACS services currently require a restart to use updated TLS certificates. This can cause downtime or connection failures, especially during CA certificate rotations (not yet enabled - see ROX-20262 ) or when existing certificates are near expiry.

Certificate hot reloading will fix the above issues, and also enable using short-lived TLS certificates (currently our TLS certificates are valid for 1y and replaced after 6m).

Acceptance Criteria:

A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

<enter general Feature acceptance here>

Success Criteria or KPIs measured:

A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.

<enter success criteria and/or KPIs here>

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

<your text here>

Out of Scope (Optional):

High-level list of items that are out of scope. Initial completion during Refinement status.

<your text here>