Add the dataMoverPrepareTimeout and resourceTimeout to the Node-Agent

[mpryc]

Add the dataMoverPrepareTimeout and resourceTimeout to the DPA's Node-Agent

Fixes #1368

Adds the following fields to the Node-Agent within the DPA:

• dataMoverPrepareTimeout How long to wait for preparing a DataUpload/DataDownload. Default is 30 minutes.
• resourceTimeout How long to wait for resource processes which are not covered by other specific timeout parameters. Default is 10 minutes.

Why the changes were made

To fix #1368

How to test the changes made

1. Run make tests
2. Manually:

• Create DPA with the following options

  configuration:
    nodeAgent:
      dataMoverPrepareTimeout: 20m
      enable: true
      resourceTimeout: 10m
      uploaderType: kopia

• In the node-agent pod shell, confirm the node-agent server is running with proper flags set:

$ tr '\0' ' ' < /proc/1/cmdline
/velero node-agent server --data-mover-prepare-timeout=20m0s --resource-timeout=10m0s

• (update DPA scenario) Modify the DPA with updated dataMoverPrepareTimeout:

  configuration:
    nodeAgent:
      dataMoverPrepareTimeout: 25m30s
      enable: true
      resourceTimeout: 10m
      uploaderType: kopia

• In the node-agent pod shell, confirm the node-agent server is running with proper flags set:

$ tr '\0' ' ' < /proc/1/cmdline
/velero node-agent server --data-mover-prepare-timeout=25m30s --resource-timeout=10m0s

• (update DPA scenario - removed timeout) Modify the DPA with removed dataMoverPrepareTimeout:

  configuration:
    nodeAgent:
      enable: true
      resourceTimeout: 15m
      uploaderType: kopia

• In the node-agent pod shell, confirm the node-agent server is running with proper flags:

$ tr '\0' ' ' < /proc/1/cmdline      
/velero node-agent server --resource-timeout=15m0s 

[mpryc]

/retest

[mpryc]

/test 4.19-e2e-test-aws

[mateusoliveira43]

/test unit-test

[mateusoliveira43]

I think PR needs rebase, since I removed this var in here 9ce4670#diff-080fe4f6649a4b1692368f7a41402aa8c6217c4ad5e5f8afe572fdd87974f939

[mateusoliveira43]

I think rebase is needed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpryc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mpryc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@mpryc: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/unit-test	e9e506f	link	true	/test unit-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.