Make ovs-vswitchd service 'other_config' option configurable

[e0ne]

No description provided.

[github-actions]

Thanks for your PR,
To run vendors CIs, Maintainers can use one of:

• /test-all: To run all tests for all vendors.
• /test-e2e-all: To run all E2E tests for all vendors.
• /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs, Maintainers can use one of:

• /skip-all: To skip all tests for all vendors.
• /skip-e2e-all: To skip all E2E tests for all vendors.
• /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
  Best regards.

[coveralls]

Pull Request Test Coverage Report for Build 12559608212

Details

• 38 of 49 (77.55%) changed or added relevant lines in 8 files are covered.
• 9 unchanged lines in 3 files lost coverage.
• Overall coverage increased (+0.02%) to 47.264%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pkg/host/internal/service/service.go	7	9	77.78%
pkg/render/render.go	16	18	88.89%
pkg/plugins/k8s/k8s_plugin.go	8	11	72.73%
pkg/host/mock/mock_host.go	0	4	0.0%

Files with Coverage Reduction	New Missed Lines	%
controllers/drain_controller_helper.go	1	63.59%
controllers/drain_controller.go	3	78.57%
controllers/generic_network_controller.go	5	74.38%

Totals
Change from base Build 12557982099:	0.02%
Covered Lines:	7211
Relevant Lines:	15257

---

💛 - Coveralls

[ykulazhenkov]

Can we use map[string]string here?

[e0ne]

I would like to support all available options, so this syntax will allow us to easly provide options like other-config:mtu!=1500

[adrianchiris]

I would like to support all available options, so this syntax will allow us to easly provide options like other-config:mtu!=1500

do we have a usecase for that for openvswitch table ?

[adrianchiris]

So, here are my thoughts on this one:

we should use same API as we have in OVSBridgeConfig e.g have OVSGlobalConfig in the pool config object
for now we can allow to set other_config keys only.

in addition we should support clearing any global configurations which were set but are not relevant anymore.
this can be done by checking the last applied status we cache or by saving which keys were set by the operator in a special key part of openvswitch table external_ids e.g external_ids:sriov-operator-owned-keys

the ExecPre we got for the systemd service of openvswitch would need to be a bit more complex to achieve that.

i wonder if we want a design doc for this one WDYT ?