BUG: NXRM needs to be pinned/tied to a specific Node in the EKS Cluster

[madpah]

Nexus Repository Manager 3 needs EBS-backed storage for the "Embedded Data" - EFS is not supported / fast enough - (see this).

As:

1. EBS volumes are not available across multiple AWS Availability Zones, and our EKS Cluster stretches multiple AWS Availability Zones
2. Sonatype recommendation is to use locally provisioned Node Storage (see this)

...we need to be sure that Nexus Repository Manager Deployment is pinned to a single Node in the EKS Cluster.

Currently, if EKS Node maintenance is performed, or Kubernetes decides to move workloads (as is its prerogative!), our Nexus Repository Manager will appear to suffer data loss as the EBS Volume will be on a different Node.