Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BackupPVC Configuration #630

Closed
seang96 opened this issue Nov 23, 2024 · 1 comment
Closed

BackupPVC Configuration #630

seang96 opened this issue Nov 23, 2024 · 1 comment

Comments

@seang96
Copy link

seang96 commented Nov 23, 2024

What steps did you take and what happened:
There are no options to configure the backup PVC configmap. #618 asked this but it was closed.

What did you expect to happen:
I want to set my RWX cephfs storageclass to read-only so it doesn't take an hour and cause replicated disk writes and slowing backup by hours.

The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Release notes for 1.15 details

Backup PVC read-only configuration

In 1.15, Velero allows you to configure the data mover backupPods to read-only mount the backupPVCs. In this way, the data mover expose process could be significantly accelerated for some storages (i.e., ceph).
To support the configuration, a new backup PVC configuration configMap is introduced.
For more information, check the document https://velero.io/docs/v1.15/data-movement-backup-pvc-configuration/.

Environment:

  • helm version (use helm version): v3.15.0",
  • helm chart version and app version (use helm list -n <YOUR NAMESPACE>): 8.0.0, v1.15
  • Kubernetes version (use kubectl version): v1.30.1
  • Kubernetes installer & version: v1.30.1+k3s1
  • Cloud provider or hardware configuration: hardware, Intel nuc 11 PCs
  • OS (e.g. from /etc/os-release): NixOS 24.05
@seang96
Copy link
Author

seang96 commented Nov 23, 2024

I figured this out, there are more detailed instructions on https://velero.io/docs/v1.15/node-agent-concurrency/.

Use value nodeAgent.extraArgs to include the arg with the configmap name you can confirm it loads properly with checking node agent logs after upgrading.

@seang96 seang96 closed this as completed Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant