Sonatype Nexus OSS Kubernetes Operator based on Operator SDK
The Nexus Operator is now supported only on OpenShift 3.9+ and Kubernetes 1.22+. Please use older versions if your environment doesn't meet these requirements.
Some users have reported that the path /nexus-data/etc/ directory is owned by the root user on Nexus community images. Please make sure that your environment mounts the property ConfigMap with the image user. Alternatively, you can apply this fix on your end.
We are working to add this fix in the next patch release.
conifigMap to openshift required SCCs. by @bdurrow in https://github.com/m88i/nexus-operator/pull/217
Full Changelog: https://github.com/m88i/nexus-operator/compare/v0.5.0...v0.6.0
The Nexus Operator deploys and controls a Nexus OSS Server on Kubernetes (1.14+) and on OpenShift (4.x+) clusters.
In this release the deployment's strategy type has been changed from "rollingUpdate" to "recreate", preventing deadlock situations when persistence is enabled (see #191). spec.replicas also has been changed due to a similar reason and its value should now be either 0 or 1, disabling horizontal scaling until #61 is implemented.
IMPORTANT: this change in deployment strategy type results in a previous deployment being deleted before the new one is created, which leads to temporary unavailability while the new deployment comes up.
Our images are published on Quay.io and our operator is listed in the OperatorHub catalog.
Please refer to the documentation. If you installed using the Operator Marketplace (OLM), the upgrade should happen automatically.
For a full list of resolved issues, please refer to the closed issues targeting this release.
The Nexus Operator deploys and controls a Nexus OSS Server on Kubernetes (1.14+) and on OpenShift (4.x+) clusters.
In this release, we changed the operator to cluster-scoped mode. This means that you can install it in its own namespace and the operands (Nexus CRs) in any namespace in the cluster. There's no need to install the operator and the operand in the same namespace any more.
Our images are published on Quay.io and our operator is listed in the OperatorHub catalog.
On OpenShift 3.11 you might need to apply our installation script using the oc client with the flag --validate=false, since we've added some fields in the Nexus CRD that are not available in this OpenShift version (Kubernetes 1.11).
Please refer to the documentation. If you installed using the Operator Marketplace (OLM), the upgrade should happen automatically.
For a full list of resolved issues, please refer to the closed issues targeting this release.
The Nexus Operator deploys and controls a Nexus OSS Server on Kubernetes (1.11+) and on OpenShift (3.11, 4.x+) clusters.
In this release we did major internal changes in the operator aiming for more stability. Among the new features, we'd like to highlight the automatic minor upgrades and the automatic creation of community maven repositories out of the box. For more details please see #132 and #5.
Our images are published on Quay.io and our operator is listed in the OperatorHub catalog.
Please refer to the documentation. If you installed using the Operator Marketplace (OLM), the upgrade should happen automatically.
For a full list of resolved issues, please refer to the closed issues targeting this release.
Minor patch to fix a problem with the operator roles in the internal manifest (CSV).
Please refer to the documentation.
See more details in the v0.2.1 milestone release notes.
The Nexus Operator deploys and controls a Nexus OSS Server on Kubernetes (1.11+) and on OpenShift (3.11, 4.x+) clusters.
In this release we worked on stability and security issues to provide users a more reliable experience while having the Nexus Server deployed in the cluster.
Due to incompatibility issues with our internal manifests and the OperatorHub catalog, we had to make some internal manifest changes. Because of this change, If you have installed the former version via OLM, you must uninstall it manually and then install this new version. In the future you won't have to do that any more, since OLM will handle the automatic updates for you.
Please refer to the documentation.