✨ Add Ironic Networking Service deployment support

[alegacy]

Implements infrastructure for deploying the Ironic Networking Service as a separate Deployment to handle Top-of-Rack switch port automation during bare metal node provisioning.

Key features:

• New NetworkingService configuration on Ironic CRD
• Separate Deployment for ironic-networking with JSON-RPC on port 6190
• External networking service endpoint configuration support
• Provider network configuration for inspection/cleaning VLANs
• Pod auto-restart on TLS certificate changes
• ClusterIP Service for Ironic-to-Networking communication
• Switch config secret lifecycle (create-if-not-exists, delete)

What this PR does / why we need it:

Partially implements: metal3-io/metal3-docs#586

Checklist:

• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• E2E tests have been added, if necessary.

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign elfosardo for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[metal3-io-bot]

Hi @alegacy. Thanks for your PR.

I'm waiting for a metal3-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[alegacy]

Created this as a draft because it has a dependency on the ironic-image PR: metal3-io/ironic-image#931

...functional tests (e2e) will failed until the ironic-image PR is merged!

[dtantsur]

/ok-to-test

[alegacy]

/retest