Sonatype Nexus Repository 3 Feature Status
Note
The Sonatype Product Development Lifecycle (PDLC), including definitions of each stage, is fully defined in Sonatype Sunsetting Information.For more information about Sonatype Support services, please see Sonatype's Software Support Policy
For more information about Sonatype Support services, please see Sonatype's Software Support Policy.
The Sonatype PDLC is designed to keep us continually improving our products and to ensure that our customers have access to our best features and functionality. This also helps us provide quality support services for our features and products. To this end, Sonatype will sunset and remove some Sonatype Nexus Repository features as they become obsolete.
Sonatype Nexus Repository 3 Feature Status Table
The following table lists Sonatype Nexus Repository features that are being sunsetted, our reasoning behind these decisions, and next steps for any impacted customers.
Sonatype Nexus Repository Feature | Status | Initial Release Date and Version | Beginning of Extended Maintenance | Sunset Date | Reasoning for Sunset | Next Steps |
High Availability Clustering (HA-C) | Sunsetted | February 2017 (3.3.0) | October 17, 2023 | April 17, 2024 | We released the updated version of High Availability in Q1 2023 with release 3.50.0. This new offering offers far superior functionality, quality, and scale. | Customers currently using HA-C and interested in using Sonatype Nexus Repository 3 in a high availability environment should upgrade to the updated HA deployment model. See our help documentation on migrating to an HA deployment from HA-C. If you're a Sonatype Nexus Repository Pro customer using HA-C and are not interested in migrating to one of our new HA deployment options, contact Support for further guidance. |
Replication v1 | Sunsetted | September 1, 2021 (3.34.0) | August 3, 2023 | December 15, 2023 | In 3.34.0, we introduced our first replication feature (Replication v1), which used a manually run replicator tool to copy binaries from one blob store to another. In 3.48.0, we introduced Content Replication as a much more user-friendly, lightweight feature to replace Replication v1. We also announced at that time that we would eventually remove Replication v1. The newer Content Replication feature is far simpler and includes more automation; it also has fewer system requirements and supports more formats. Customers needing a way to make artifacts readily available across distributed teams should use the newer Content Replication feature. | As Content Replication is an entirely different and separate feature from Replication v1, there is no direct migration path. Those wishing to implement Content Replication should follow our Content Replication implementation documentation. |
Red Hat OpenShift Operator and Container (Embedded OrientDB version) | Sunsetted | June 2020 (3.24.0) | August 3, 2023 | December 15, 2023 | Sonatype does not recommend using this container/operator due to data corruption risks when running the embedded OrientDB database inside container orchestration (Kubernetes, OpenShift). | In October 2023, Sonatype published a new OpenShift Operator for Sonatype Nexus Repository Pro. The new operator uses an external PostgreSQL database and supports our High Availability deployment options. See Installing Sonatype Nexus Repository Using the OpenShift Operator. |
FAQ
Replication v1
Why should I upgrade from Replication v1 to Content Replication?
Replication v1 has been replaced by Content Replication . Upgrading provides the following benefits:
Easier to Deploy: There is no longer a need for a ‘replicator’. Feedback around ‘Repository Replication’ released in late 2021 suggested it was challenging to deploy ‘replicator,’ so we have entirely redesigned the feature to remove the need for it.
Easier to Connect: Content can now be transferred via HTTP instead of RSync, making this functionality agnostic to the blob store type.
More straightforward UI: The feature is now accessible through the proxy repository creation page through a single checkbox, making it easier to access and set up.
More reliable: Built on top of existing ‘hosted/proxy’ functionality that has been deployed at scale by hundreds of enterprises, making this feature much more robust.
What are the recommended alternatives or migration paths?
As Content Replication is an entirely different and separate feature from Replication v1, there is no direct migration path. Those wishing to implement Content Replication should follow our Content Replication implementation documentation .
What is the timeline for sunsetting Replication v1?
Replication v1 will sunset onDecember 15th, 2023. Customers are no longer able to access the feature on that date.
OpenShift Operator
Will there be a replacement OpenShift offering? When?
In October 2023, Sonatype published a new OpenShift Operator for Sonatype Nexus Repository Pro. The new operator uses an external PostgreSQL database and supports our High Availability deployment options.
See Installing Sonatype Nexus Repository Using the OpenShift Operator.
Why is the current OpenShift Operator being sunsetted?
The current Nexus Repository OpenShift Operator utilizes an embedded OrientDB database. Sonatype does not recommend using an OrientDB for Kubernetes/OpenShift deployments due to data corruption risks when running this embedded database within container orchestration.
What are my options for upgrading before the replacement offering becomes available?
We recommend you wait for the new operator to become available, at which time there will be a documented process for migrating. If you would prefer not to wait, we have YAML files for deploying with Kubernetes.