-
I currently have a Harbor setup that uses MinIO as the backend storage. This works fine, but I'd like to move away from MinIO. I use Longhorn as my PVC storage layer. I'm considering using a PVC to store all the container image blobs.
Context: |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
I think the issue is about |
Beta Was this translation helpful? Give feedback.
-
Maybe I'm a little late, but if anyone has the same question. |
Beta Was this translation helpful? Give feedback.
-
Replication allows user to replicate all projects and artifacts to another harbor. |
Beta Was this translation helpful? Give feedback.
-
After fiddling, I finally managed to set some time aside and I was able to migrate all the image blobs from MinIO to a Volume. Thanks in to @phin1x for their input. As noted by @chlins Harbor seems to recommend having 2 registries, so this method is likely unsupported. Here are the steps I followed
At this point,
Once you've been able to validate you're able to pull and push images, you may delete the relevant MinIO bucket or instance.. apiVersion: v1
kind: Pod
metadata:
name: minio-client
spec:
containers:
- name: minio-client
image: minio/mc:latest
command: ["/bin/sleep"]
args: ["86400"]
imagePullPolicy: IfNotPresent
volumeMounts:
- name: harbor-storage-vol
mountPath: /longhorn
volumes:
- name: harbor-storage-vol
persistentVolumeClaim:
claimName: harbor-storage-pvc |
Beta Was this translation helpful? Give feedback.
I think the issue is about
how to migrate the minio based storage to the longhorn based PVC?
, we have no experience for that but normally a safe way is you can setup a new harbor instance with the new storage and replicate the images from the old one.