**BB- Product Improvement & Maintenance (Value Stream Initiative)**  ## Description Migrate Big Bang package HelmRelease `spec.releaseName` handling in controlled phases to reduce duplicate naming patterns (for example `<namespace>-<name>-...`) while preserving upgrade safety. This epic will coordinate package-by-package rollout, dependency updates, and validation gates so we do not repeat the all-at-once failure pattern from prior attempts. ## Customer or Stakeholder Sponsor (Please do not include CUI or any sensitive program or personnel names) - Big Bang platform stakeholders (Anchors + package maintainers) driving operational consistency and maintainability. - Originating request: `big-bang/bigbang#680`. - Problem to solve: inconsistent Helm release naming, difficult-to-read resource names, and hardcoded references that currently block a safe global migration. ## Value to user of BB Users get more predictable and readable release/resource naming, lower confusion when troubleshooting, and better consistency across packages. This epic supports roadmap goals around operational reliability and safer upgrades by explicitly validating name-dependent integrations before rollout. ## Requirements/Scope - Define and publish phased migration plan for package `releaseName` updates. - Implement package-level migration waves (small batches), not a repo-wide flip. - For each migrated package: - set/standardize HelmRelease `releaseName` behavior, - update dependent hardcoded references in Big Bang and package repos, - run CI and upgrade validation from prior supported BB release, - document upgrade notes and rollback path. - Track completion in linked child issues by package/wave. ## Out of Scope - One-shot migration of all packages in a single MR. - Unbounded renaming of unrelated Kubernetes resources. - Refactors not required to support `releaseName` migration safety. ## Duration Estimated 6-10 weeks, depending on package repo coordination and upgrade test stability. ## Team - Big Bang Anchors - Package maintainers across Big Bang and downstream package repositories - CI/release support contributors ## Epic Team Members - Epic lead: TBD - Implementation owners per migration wave: TBD - Reviewer group: Anchors + affected package maintainers ## Dependencies - `big-bang/bigbang#680` - Coordination with package repos where service/resource names are hardcoded. - CI capacity for package-specific and upgrade testing. - Agreement on migration wave ordering and acceptance gates. ## Risks - Upgrade disruption if release name changes are not paired with dependent reference updates. - Hidden hardcoded references in package templates, tests, and network policies. - Cross-repo sequencing delays. - Increased merge conflicts if many package migrations are active concurrently. ## Acceptance Criteria - Migration plan and wave backlog approved and linked to this epic. - Each migrated package has: - merged implementation MR, - passing CI and upgrade validation evidence, - documented upgrade impact/notes, - rollback guidance. - No unresolved critical incidents attributable to releaseName migration. - Final issue update summarizes migrated packages, deferred packages, and rationale. ## Related Issues and/or Epics - `https://repo1.dso.mil/big-bang/bigbang/-/issues/680` - Child issues to be created per migration wave/package (link here as they are opened). ## How this epic maps to Big Bang OKRs This epic supports Big Bang reliability and operability objectives by making package release naming consistent and migration-safe. It reduces operational ambiguity and avoids risky broad-scope changes by enforcing phased validation. ## How does this proposed work benefit the enterprise using Big Bang and/or end user SRE? Enterprises and SREs get clearer resource naming, simpler runbook execution, and lower incident risk during upgrades because naming changes are validated incrementally with explicit rollback paths. ## How does this benefit the internal Big Bang team The team gets a repeatable migration framework for naming-affecting changes, reduced firefighting from all-at-once rollouts, and better cross-repo coordination through scoped wave issues and acceptance gates.