Allow network providers to accept configuration (aka calico log level to be configured)

[jar349]

1. Describe IN DETAIL the feature/behavior/change you would like to see.
   I would like to be able to configure the log level of calico from kops because kops is the entity that set it up for me.

2. Feel free to provide a design supporting your feature request.
   When passing --networking=calico to kops during cluster creation, it might be a good idea to also offer --networking-opt key=value similar to how docker allows --dns-option, --security-opt, --log-opts, etc

The modules that know how to setup each network provider should also know how to handle network-opts

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[tomcruz17]

Was looking for this feature as well because Calico's default log level of INFO seems to be too noisy and causes some wasted log storage for us.

We do have a workaround. But just in case, can this be implemented natively in kops similar to #8276

i.e.

  networking:
    calico:
      env:
      - name: FELIX_LOGSEVERITYSCREEN
        value: "warning"