Current decision is to use the existing swf bundle to deploy Nexus into the eks-d management cluster to use as a permanent eks-d registry mirror. Avoids needing to design and implement a bespoke solution just for the eks-d registry mirror.
This will involve deploying the existing bundle with the -p flag on the uds command set to only deploy nexus and its dependencies. This will require configuring external dependencies for the bundle to deploy to the management cluster just like would be needed for an environment deploying the full bundle (excluding dependencies for packages that aren't being deployed).
External dependencies required are postgres databases for keycloak and nexus, buckets for loki, velero, and zarf registry, a storage container and file server for nutanix-csi, certificates for admin and tenant gateways, and DNS entries for databases and nutanix file-server.
Current decision is to use the existing swf bundle to deploy Nexus into the eks-d management cluster to use as a permanent eks-d registry mirror. Avoids needing to design and implement a bespoke solution just for the eks-d registry mirror.
This will involve deploying the existing bundle with the -p flag on the uds command set to only deploy nexus and its dependencies. This will require configuring external dependencies for the bundle to deploy to the management cluster just like would be needed for an environment deploying the full bundle (excluding dependencies for packages that aren't being deployed).
External dependencies required are postgres databases for keycloak and nexus, buckets for loki, velero, and zarf registry, a storage container and file server for nutanix-csi, certificates for admin and tenant gateways, and DNS entries for databases and nutanix file-server.