OCP/Telco Definition of Done
Epic Template descriptions and documentation.

Epic Goal

• Refine ClusterVersion status.history's pruning to balance "I want some history information, and some history is more interesting than others" against "I want a bounded ClusterVersion resource size" with the minimal conflict.

Why is this important?

• Unbounded ClusterVersion object growth is unsustainable.  Eventually we'd run up against Kubernetes/etcd resource-size limits.
• The oldest version in the history (which is what we throw out today) is often very interesting, because some cluster state is created at install-time and never managed since.  We want to throw out something less interesting, when we have to throw something out.

Scenarios

1. I have a cluster that updates a lot.  Today I eventually lose track of when it was installed.  After this epic, we'll preserve that install version  (in clusters where it hasn't already been forgotten) and instead throw out something less interesting.

Acceptance Criteria

• smarter pruning.
• unit tests.  Probably no need for e2e or anything like that.
• web-console UX improvements to reflect the fact that history may be gapped.  No oc history viewer besides oc get ..., so that's fine.
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. enhancement approval
2. openshift/api approval
3. web-console copy-edits

Done Checklist

• [ ] CI - CI is running, tests are automated and merged.
• [ ] Release Enablement <link to Feature Enablement Presentation>
• [ ] DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>[ ]
• [ ] DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• [ ] DEV - Downstream build attached to advisory: <link to errata>
• [ ] QE - Test plans in Polarion: <link or reference to Polarion>
• [ ] QE - Automated tests merged: <link or reference to automated tests>
• [n/a] DOC - Downstream documentation merged: <link to meaningful PR>