Linux windows hybrid deploy

[Lyndon-Li]

Fix issue #8416, #8417, deploy Velero server and node-agent in linux/Windows hybrid env:

• Velero server is restricted to run on linux nodes only
• node-agent is divided into two instances. node-agent instance runs in linux nodes only and node-agent-windows runs in Windows only
• node-agent daemonset is deployed when --use-node-agent is specified; node-agent-windows daemonset is deployed when --use-node-agent-windows is specified
• In a pure linux nodes cluster, desiredNumberScheduled for node-agent-windows is 0
• In a pure Windows nodes cluster, desiredNumberScheduled for node-agent is 0
• In a hybrid cluster, desiredNumberScheduled for node-agent-windows is the number of Windows nodes; desiredNumberScheduled for node-agent is the number of linux nodes

[codecov]

Codecov Report

Attention: Patch coverage is 52.33645% with 51 lines in your changes missing coverage. Please review.

Project coverage is 59.19%. Comparing base (010fd1c) to head (4ad9c24).
Report is 12 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/cmd/server/server.go	0.00%	19 Missing ⚠️
pkg/cmd/cli/nodeagent/server.go	0.00%	17 Missing ⚠️
pkg/cmd/cli/install/install.go	0.00%	8 Missing ⚠️
pkg/install/resources.go	53.84%	4 Missing and 2 partials ⚠️
pkg/nodeagent/node_agent.go	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8504      +/-   ##
==========================================
+ Coverage   59.18%   59.19%   +0.01%     
==========================================
  Files         369      369              
  Lines       39329    39408      +79     
==========================================
+ Hits        23276    23327      +51     
- Misses      14585    14612      +27     
- Partials     1468     1469       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Lyndon-Li]

This retry is to resolve the problem that in some Windows env, the pod network is not immediately ready. Without this, the pod may restart for several times

[Lyndon-Li]

Technically, we don't need to distinguish different OS types for install, node-agent and node-agent-windows ds instance could be installed in both OS all the time.
I don't see any problem about this, but let me know if you have any concern about the same. @sseago @shubham-pampattiwar @kaovilai @reasonerjt @blackpiglet @anshulahuja98

[kaovilai]

I don't see a problem with 0 scheduled daemonsets. It's not taking up any major resources.

[reasonerjt]

Thanks @Lyndon-Li
I have 2 overall comments:

1. I think we can add the labels/annotations to make sure velero-server is always running on Linux worker-node.
2. We should add a flag like " --windows-support" and only when this flag is true we deploy the daemonset for Windows so by default everything stays the same.

[Lyndon-Li]

Thanks @Lyndon-Li I have 2 overall comments:

1. I think we can add the labels/annotations to make sure velero-server is always running on Linux worker-node.
2. We should add a flag like " --windows-support" and only when this flag is true we deploy the daemonset for Windows so by default everything stays the same.

As the discussion:
For 1, we will force Velero to run in linux nodes only. We will add a clarification in release notes --- Velero requires at least one linux worker node in order to run with Windows nodes.
For 2, we will add a flag --use-node-agent-windows to install node-agent-windows daemonset.