vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
velero/site/docs/v0.11.0/expose-minio.md

2.4 KiB
Raw Blame History

Expose Minio outside your cluster

When you run commands to get logs or describe a backup, the Velero server generates a pre-signed URL to download the requested items. To access these URLs from outside the cluster -- that is, from your Velero client -- you need to make Minio available outside the cluster. You can:

  • Change the Minio Service type from ClusterIP to NodePort.
  • Set up Ingress for your cluster, keeping Minio Service type ClusterIP.

In Velero 0.10, you can also specify the value of a new publicUrl field for the pre-signed URL in your backup storage config.

For basic instructions on how to install the Velero server and client, see the getting started example.

Expose Minio with Service of type NodePort

The Minio deployment by default specifies a Service of type ClusterIP. You can change this to NodePort to easily expose a cluster service externally if you can reach the node from your Velero client.

You must also get the Minio URL, which you can then specify as the value of the new publicUrl field in your backup storage config.

  1. In examples/minio/00-minio-deployment.yaml, change the value of Service spec.type from ClusterIP to NodePort.

  2. Get the Minio URL:

    • if you're running Minikube:

      minikube service minio --namespace=velero --url

    • in any other environment:

      1. Get the value of an external IP address or DNS name of any node in your cluster. You must be able to reach this address from the Velero client.

      2. Append the value of the NodePort to get a complete URL. You can get this value by running:

        kubectl -n velero get svc/minio -o jsonpath='{.spec.ports[0].nodePort}'

  3. In examples/minio/05-backupstoragelocation.yaml, uncomment the publicUrl line and provide this Minio URL as the value of the publicUrl field. You must include the http:// or https:// prefix.

Work with Ingress

Configuring Ingress for your cluster is out of scope for the Velero documentation. If you have already set up Ingress, however, it makes sense to continue with it while you run the example Velero configuration with Minio.

In this case:

  1. Keep the Service type as ClusterIP.

  2. In examples/minio/05-backupstoragelocation.yaml, uncomment the publicUrl line and provide the URL and port of your Ingress as the value of the publicUrl field.