Velero external endpoint not considered

[FedericoAntoniazzi]

When enabling the DR module with an external endpoint configured, furyctl also installs a MinIO instance inside the kube-system namespace and still uses the default endpoints and credentials.

Snippet

furyctl.yaml:

...
      dr:
        type: on-premises
        velero:
          externalEndpoint:
            accessKeyId: REDACTED
            bucketName: velero
            endpoint: other.minio.instance:9000
            insecure: true
            secretAccessKey: REDACTED
...

[nutellinoit]

Which version are you using?

[FedericoAntoniazzi]

furyctl v0.28.0 and distribution v1.28.0

[Al-Pragliola]

you should set .velero.backend to "externalEndpoint" because the default value is "minio": (https://github.com/sighupio/fury-distribution/blob/main/defaults/onpremises-kfd-v1alpha2.yaml#L222)

      dr:
        type: on-premises
        velero:
          backend: externalEndpoint
          externalEndpoint:
            accessKeyId: REDACTED
            bucketName: velero
            endpoint: other.minio.instance:9000
            insecure: true
            secretAccessKey: REDACTED

to improve the UX maybe we should add a validation to that field

[FedericoAntoniazzi]

Thank you @Al-Pragliola, I missed that field. What to do in case of installing velero in a EKS cluster? Should we set type: on-premises even if we only need the external endpoint?

[Al-Pragliola]

The schema for an EKSCluster is different, here's an example:

      dr:
        type: eks
        velero:
          eks:
            bucketName: example-velero
            region: eu-west-1

[nutellinoit]

On EKS, velero do it's backup to an s3 bucket that furyctl manages, there is no externalEndpoint feature on that provider