Remove nexusRepositoryManager package from Big Bang umbrella

Umbrella Chart Change

Description

Fully removes the deprecated nexusRepositoryManager addon from the Big Bang umbrella chart. All users should migrate to the maintained NXRM-HA package.

Changes

• Deleted chart/templates/nexus-repository-manager/ (7 template files: helmrelease, gitrepository, values, namespace, git-credentials, imagepullsecret, secret-ca)
• Removed nexusRepositoryManager section from chart/values.yaml (68 lines)
• Removed nexusRepositoryManager schema definition from chart/values.schema.json
• Cleaned chart/templates/NOTES.txt of nexus deprecation notices, variable definitions, and SSO blocks
• Cleaned chart/templates/kyverno-policies/values.yaml of nexus namespace and pod allow entries
• Removed nexus unit test from chart/unittests/packages/helmrelease/helmrelease_test.yaml
• Cleaned all test values files (test-values.yaml, eks-test-values.yaml, rke2-test-values.yaml, openshift-test-values.yaml, oci-values.yaml, package-mapping.yaml)
• Deleted docs/packages/addons/nexus-repository-manager.md and cleaned 14 other docs files of nexus references

33 files changed, 8 insertions, 847 deletions

For Issue

Closes #3193 (closed)

Upgrade Notices

Important: nexusRepositoryManager Addon Removed

The legacy nexusRepositoryManager addon has been removed from the Big Bang umbrella chart. Users requiring Nexus Repository Manager should migrate to the maintained NXRM-HA package.

NXRM-HA provides:

• High Availability Support: Deploy Nexus Repository Manager Pro in a highly available, multi-node configuration
• Production-Ready Architecture: Built-in support for external databases (PostgreSQL, AWS RDS) and object storage
• Enterprise features including clustering and replication
• Active maintenance directly from Sonatype
• Better resource management and horizontal scaling capabilities

Migration Required

Upgrading from the legacy nexus-repository-manager chart to nxrm-ha requires a migration process. This is NOT a simple in-place upgrade. Key requirements:

• Plan downtime for the migration
• Back up all data before migrating
• Test in non-production environments first
• Note that the namespace, resource naming conventions, and configuration structure have changed
• Configuration is now under an upstream: key
• PostgreSQL is now required

See NXRM-HA MR#29 Upgrade Notices for full migration details.