k8up-io / k8up

Kubernetes and OpenShift Backup Operator
https://k8up.io/
Apache License 2.0
696 stars 66 forks source link

Allow setting subpaths for S3 backend #615

Open cwrau opened 2 years ago

cwrau commented 2 years ago

Summary

As user I want to specify subpaths for the S3 backend So that I can have a nice structure in my S3

Context

I want the backups to be grouped by namespace, helmRelease and type, resulting in the following;

HelmRelase customer-prod in namespace customer backs up PVC config. I want the backups to land in the following location;

s3://k8s-backup/customer/customer-prod/persistentvolumeclaim/config/

Out of Scope

No response

Further links

Acceptance Criteria

Implementation Ideas

An (optional) prefix field on the S3Spec

s4ndalHat commented 1 month ago

Hello, also need this feature, is this on going ? Thanks

Kidswiss commented 1 month ago

Hi everyone

You can use subpaths S3 like this:

apiVersion: k8up.io/v1
kind: Backup
metadata:
  name: test
spec:
  backend:
    repoPasswordSecretRef:
      key: password
      name: k8up-repository-password
    s3:
      accessKeyIDSecretRef:
        key: AWS_ACCESS_KEY_ID
        name: backup-bucket-credentials
      bucket: mybucket/path/to/subfolder
      endpoint: http://minio-server.minio.svc:9000
      secretAccessKeySecretRef:
        key: AWS_SECRET_ACCESS_KEY
        name: backup-bucket-credentials

The bucket field is simply concatenated to build the RESTIC_REPOSITORY string as documented here: https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#amazon-s3.

So you can simply add the subfolders via slashes.

s4ndalHat commented 1 month ago

@Kidswiss thanks! Its getting configured, thank you..

However, I'm facing another issue, I'm getting the following error : image

Kidswiss commented 1 month ago

@s4ndalHat the ciphertext verification failed error can have two causes I'm aware of:

s4ndalHat commented 1 month ago

This is where I'm lost, it's my first backup and I'm always trying into a new repository and bucket... always the same issue :')

Kidswiss commented 1 month ago

Can you please open a new issue and add you manifests?

s4ndalHat commented 1 month ago

My bad, I reverted the endpoint url and bucket typo, I'm still getting some minor error but the job is succeded.

Instead typing: url: myurl and bucket: /path/to/myprefix, I typed url: myurl/bucket and bucket: myprefix

Sorry, but its getting working (next I'll be testing the restore process)