Nexus Operator v0.6.0

Breaking change!

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.

Known Configuration Issues

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.

What's Changed

• Add way to provide annotations to ingress/route resources by @LCaparelli in #206
• The PR aims to improve the handling of WATCH_NAMESPACE param when ins… by @Kaitou786 in #202
• Allow setting host and labels for Route/Ingress by @LCaparelli in #207
• Add way to specify extra volumes by @LCaparelli in #208
• Allow ignoring updates to networking resources by @LCaparelli in #210
• Closes #204 - Mounting nexus.properties in a ConfigMap by @ricardozanini in #212
• Fix #214 Upgrade CRD to v1 and remove Legacy Ingress by @ricardozanini in #215
• Add conifigMap to openshift required SCCs. by @bdurrow in #217

New Contributors

• @bdurrow made their first contribution in #217

Full Changelog: v0.5.0...v0.6.0

Nexus Operator v0.5.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.

Installation

Please refer to the documentation.
If you installed using the Operator Marketplace (OLM), the upgrade should happen automatically.

Enhancements

• #198 - Upgrade to Go v1.15.6
• #199 - Upgrade to operator-sdk v1.2.0

Bug Fixes

• #191 - Pod fails to start after modifying the Nexus resource

For a full list of resolved issues, please refer to the closed issues targeting this release.

Nexus Operator v0.4.0

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.

Breaking Change

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).

Installation

Please refer to the documentation.
If you installed using the Operator Marketplace (OLM), the upgrade should happen automatically.

Bug Fixes

• #151 - Correct mention of Ingress Controllers on CSV
• #157 - Server operations don't work when the Nexus CR is in a different namespace

Enhancements

• #140 - Upgrade to Operator SDK 1.0.0 and new Manifest Bundle
• #143 - Make logs prefixed with the namespace and name of the Nexus being reconciled
• #149 - Add Maven Public repository URL to the Nexus CR Status
• #158 - Tighten up the Role permissions
• #161 - Nexus Operator as a Cluster Scoped Operator
• #180 - When available, use networking.k8s.io/v1 API version for Ingresses

Known Issues

• #129 - When exposing Nexus via NGINX Ingress on Kubernetes, users might see 413 request entity too large error

For a full list of resolved issues, please refer to the closed issues targeting this release.

Nexus Operator v0.3.0

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.

Installation

Please refer to the documentation.
If you installed using the Operator Marketplace (OLM), the upgrade should happen automatically.

Bug Fixes

• #141 - Handle conflict updates when updating Nexus CR
• #137 - Deployments are deemed different even if there are no changes in the Nexus CR
• #73 - Ingress comparison is not working as expected bug bug

Enhancements

• #132 - Implement seamless upgrade for the community image
• #83 - Allow the user to select the Pull Policy
• #80 - Add Nexus3 health check using its own API endpoint
• #67 - Customize Nexus service liveness/readiness
• #51 - Add SCC to the Service Account in OCP
• #5 - Unless specified otherwise, the operator should create Apache, JBoss and Red Hat maven proxies
• #3 - Add an option to set admin default password for new installations

Known Issues

• #129 - When exposing Nexus via NGINX Ingress on Kubernetes, users might see 413 request entity too large error

For a full list of resolved issues, please refer to the closed issues targeting this release.

Nexus Operator v0.2.1

Minor patch to fix a problem with the operator roles in the internal manifest (CSV).

Installation

Please refer to the documentation.

Bug Fixes

• #64 Nexus Operator fails to create a ServiceAccount for the deployed CR

See more details in the v0.2.1 milestone release notes.

Nexus Operator v0.2.0

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.

WARNING

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.

Installation

Please refer to the documentation.

Bug Fixes

• #24 Image status are not displaying correct
• #25 Nexus fails when deployed without persistence
• #40 The Operator fails to start on Openshift 3.x
• #41 Pods can't be started on OCP 3.x clusters with default configuration

Enhancements

• #13 Adjust INSTALL4J_ADD_VM_PARAMS to follow Resources Requirements
• #20 Add TLS support
• #31 Migrate to Operator SDK 0.17.0 and Go 1.14
• #32 Improve OLM Integration

Know Issues

• #51 Add SCC to the Service Account in OCP