mirror of
https://github.com/vmware-tanzu/velero.git
synced 2025-12-23 14:25:22 +00:00
Merge pull request #9167 from blackpiglet/fix_repository_maintenance_doc
Some checks failed
Run the E2E test on kind / build (push) Failing after 11m13s
Run the E2E test on kind / setup-test-matrix (push) Successful in 3s
Run the E2E test on kind / run-e2e-test (push) Has been skipped
Main CI / Build (push) Failing after 30s
Close stale issues and PRs / stale (push) Successful in 13s
Trivy Nightly Scan / Trivy nightly scan (velero, main) (push) Failing after 1m14s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-aws, main) (push) Failing after 1m23s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-gcp, main) (push) Failing after 1m9s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-microsoft-azure, main) (push) Failing after 1m8s
Some checks failed
Run the E2E test on kind / build (push) Failing after 11m13s
Run the E2E test on kind / setup-test-matrix (push) Successful in 3s
Run the E2E test on kind / run-e2e-test (push) Has been skipped
Main CI / Build (push) Failing after 30s
Close stale issues and PRs / stale (push) Successful in 13s
Trivy Nightly Scan / Trivy nightly scan (velero, main) (push) Failing after 1m14s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-aws, main) (push) Failing after 1m23s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-gcp, main) (push) Failing after 1m9s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-microsoft-azure, main) (push) Failing after 1m8s
Fix the repository-maintenance-job-configmap format issue in doc.
This commit is contained in:
@@ -60,15 +60,22 @@ This can be done by adding multiple entries in the `LoadAffinity` array.
|
||||
|
||||
The sample of the ```repo-maintenance-job-configmap``` ConfigMap for the above scenario is as below:
|
||||
``` bash
|
||||
cat <<EOF > repo-maintenance-job-config.json
|
||||
cat <<EOF > repo-maintenance-job-config.yaml
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: repo-maintenance-job-config
|
||||
namespace: velero
|
||||
data:
|
||||
global: |
|
||||
{
|
||||
"global": {
|
||||
"podResources": {
|
||||
"cpuRequest": "100m",
|
||||
"cpuLimit": "200m",
|
||||
"memoryRequest": "100Mi",
|
||||
"memoryLimit": "200Mi"
|
||||
},
|
||||
"keepLatestMaintenanceJobs": 1,
|
||||
"loadAffinity": [
|
||||
{
|
||||
"nodeSelector": {
|
||||
@@ -100,6 +107,15 @@ cat <<EOF > repo-maintenance-job-config.json
|
||||
}
|
||||
]
|
||||
}
|
||||
kibishii-default-kopia: |
|
||||
{
|
||||
"podResources": {
|
||||
"cpuRequest": "200m",
|
||||
"cpuLimit": "400m",
|
||||
"memoryRequest": "200Mi",
|
||||
"memoryLimit": "400Mi"
|
||||
},
|
||||
"keepLatestMaintenanceJobs": 2
|
||||
}
|
||||
EOF
|
||||
```
|
||||
@@ -110,7 +126,7 @@ The nodes matching one of the two conditions are selected.
|
||||
|
||||
To create the configMap, users need to save something like the above sample to a json file and then run below command:
|
||||
```
|
||||
kubectl create cm repo-maintenance-job-config -n velero --from-file=repo-maintenance-job-config.json
|
||||
kubectl apply -f repo-maintenance-job-config.yaml
|
||||
```
|
||||
|
||||
### Log
|
||||
|
||||
Reference in New Issue
Block a user