Skip to content

Modify the repository-maintenance.md for the label and annotation change #8977

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.

Sign up for GitHub

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

Closed
blackpiglet wants to merge 1 commit into from
Closed

Modify the repository-maintenance.md for the label and annotation change #8977

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions site/content/docs/main/repository-maintenance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,9 +155,13 @@ Status:
- `Recent Maintenance` keeps the status of the recent 3 maintenance jobs, including its start time, result (succeeded/failed), completion time (if the maintenance job succeeded), or error message (if the maintenance failed)

### Others
Maintenance jobs will inherit the labels, annotations, toleration, nodeSelector, service account, image, environment variables, cloud-credentials etc. from Velero deployment.
Maintenance jobs will not run for backup repositories whose backup storage location is set as readOnly.
Maintenance jobs will inherit the service account, image, environment variables, cloud-credentials, volumes, etc. from Velero deployment.
Maintenance jobs will not run for backup repositories whose backup storage location is set as readOnly.

Please notice the Maintenance job's labels and annotations are not inherited from the Velero deployment.
Velero keeps [allowlists][4] for the labels and annotations now. Please submit PRs to add the ones you need.

[1]: velero-install.md#usage
[2]: node-agent-concurrency.md
[3]: backup-repository-configuration.md#full-maintenance-interval-customization
[4]: https://github.com/vmware-tanzu/velero/blob/v1.16.1/pkg/util/third_party.go
8 changes: 6 additions & 2 deletions site/content/docs/v1.16/repository-maintenance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,9 +155,13 @@ Status:
- `Recent Maintenance` keeps the status of the recent 3 maintenance jobs, including its start time, result (succeeded/failed), completion time (if the maintenance job succeeded), or error message (if the maintenance failed)

### Others
Maintenance jobs will inherit the labels, annotations, toleration, nodeSelector, service account, image, environment variables, cloud-credentials etc. from Velero deployment.
Maintenance jobs will not run for backup repositories whose backup storage location is set as readOnly.
Maintenance jobs will inherit the service account, image, environment variables, cloud-credentials, volumes, etc. from Velero deployment.
Maintenance jobs will not run for backup repositories whose backup storage location is set as readOnly.

Please notice the Maintenance job's labels and annotations are not inherited from the Velero deployment.
Velero keeps [allowlists][4] for the labels and annotations now. Please submit PRs to add the ones you need.

[1]: velero-install.md#usage
[2]: node-agent-concurrency.md
[3]: backup-repository-configuration.md#full-maintenance-interval-customization
[4]: https://github.com/vmware-tanzu/velero/blob/v1.16.1/pkg/util/third_party.go
Loading