velero install doesn't honored "--node-agent-pod-cpu-limit / --node-agent-pod-mem-limit"

4 views
Skip to first unread message

Tzahi Ashkenazi

unread,
Feb 14, 2024, 2:30:35 AM2/14/24
to Project Velero
Hi Team 
when running the velero installation  script  as follow : 
./velero install \
    --provider aws \
    --image velero/velero:v1.12.3 \
    --plugins velero/velero-plugin-for-aws:latest,quay.io/konveyor/openshift-velero-plugin:latest,velero/velero-plugin-for-csi:main --bucket ${bucket_name} \
    --secret-file ${bucket_credentials_location} \
    --use-node-agent \
    --use-volume-snapshots=false \
    --namespace=${namespace} \
    --backup-location-config s3Url=${minio_url},insecureSkipTLSVerify=true,profile=default,region=minio=minio,s3ForcePathStyle=true \
    --features=EnableCSI --prefix "velero" \
    --velero-pod-cpu-limit "2000m" --velero-pod-mem-limit "2048Mi" \
    --node-agent-pod-cpu-limit "20000m" --node-agent-pod-mem-limit "32Gi" \

the node-agent cpu & memory limitation doesnt honored by the script 

we manage to checge those values after the installtion completed by editing the deamon-set object using oc command 

how can we reslove this matter from the velero installation script  



Reply all
Reply to author
Forward
0 new messages