Implement (external) logs/describe/details via fileserver for velero cli - fixes #12

[EugenMayer]

This PR introduces the ability to download the velero logs, describe backups and show details via an ingress / external access. Fixing #12

For this new (optional) plugin configurations are offered

  externalDownloadHostname: "www.velero-logs.domain.com"
  # using https currently seems not to be supported by the velero client
  externalDownloadScheme: "http"
  externalDownloadPort: 80

Not setting those will default to the old behavior instructing the velero cli to download the logs using the internal pod ip of the fileserver (which always fails).

When providing those, including

• deploying a service for the fileserver (see examples/fileserverService)
• an ingress for this service, in our case here www.velero-logs.domain.com

You will be able to download the velero logs when running velero backup logs manual1.

You can test it yourself by using my test image ghcr.io/eugenmayer/local-volume-provider:0.7.3

apiVersion: v1
kind: ConfigMap
metadata:
  name: local-volume-provider-config
  namespace: velero
  labels:
    velero.io/plugin-config: ""
    replicated.com/nfs: ObjectStore
    replicated.com/hostpath: ObjectStore
data:
  fileserverImage: ghcr.io/eugenmayer/local-volume-provider:0.7.3
  externalDownloadHostname: "www.velero-logs.domain.com"
  externalDownloadScheme: "http"
  externalDownloadPort: 80

Known limitations

it seems like the velero cli is not able to download the logs from a TLS ingress (official signed LE certificate). it always fails with.

An error occurred: request failed: Bad Request

Assuming this is a velero limitation right now, created an issue vmware-tanzu/velero#8677