Fixing paths to proper destination in main README
Old paths lead to 404. Paths have been updated to proper ones.
This commit is contained in:
parent
3169701546
commit
9fd454a8dd
@ -2,12 +2,12 @@
|
|||||||
|
|
||||||
We provide Helm charts for two different deployment scenarios:
|
We provide Helm charts for two different deployment scenarios:
|
||||||
|
|
||||||
See the [AWS Single-Instance Resiliency Chart](./https://github.com/sonatype/nxrm3-helm-repository/tree/main/aws-single-instance-resiliency) if you are doing the following:
|
See the [AWS Single-Instance Resiliency Chart](https://github.com/sonatype/nxrm3-helm-repository/tree/main/aws-single-instance-resiliency) if you are doing the following:
|
||||||
* Deploying Nexus Repository Pro to an AWS cloud environment with the desire for automatic failover across Availability Zones (AZs) within a single region
|
* Deploying Nexus Repository Pro to an AWS cloud environment with the desire for automatic failover across Availability Zones (AZs) within a single region
|
||||||
* Planning to configure a single Nexus Repository Pro instance within your Kubernetes/EKS cluster with two or more nodes spread across different AZs within an AWS region
|
* Planning to configure a single Nexus Repository Pro instance within your Kubernetes/EKS cluster with two or more nodes spread across different AZs within an AWS region
|
||||||
* Using an external PostgreSQL database (required)
|
* Using an external PostgreSQL database (required)
|
||||||
|
|
||||||
See the [Single-Instance OSS/Pro Kubernetes Chart](./https://github.com/sonatype/nxrm3-helm-repository/tree/main/single-inst-oss-pro-kubernetes) if you are doing the following:
|
See the [Single-Instance OSS/Pro Kubernetes Chart](https://github.com/sonatype/nxrm3-helm-repository/tree/main/single-inst-oss-pro-kubernetes) if you are doing the following:
|
||||||
* Using embedded OrientDB (required)
|
* Using embedded OrientDB (required)
|
||||||
* Deploying either Nexus Repository Pro or OSS to an on-premises environment with bare metal/VM server (Node)
|
* Deploying either Nexus Repository Pro or OSS to an on-premises environment with bare metal/VM server (Node)
|
||||||
* Deploying a single Nexus Repository instance within a Kubernetes cluster that has a single Node configured
|
* Deploying a single Nexus Repository instance within a Kubernetes cluster that has a single Node configured
|
||||||
|
Loading…
x
Reference in New Issue
Block a user