Provisioner: customize the 'bootstrap's cmdline param: dns-lookup-family

[izturn]

Signed-off-by: Gang Liu [email protected]

When running in the v4 environment, the default auto will trigger annoying CoreDNS logs likes:

[Info] 10.21.16.16:38784 - 19433 "AAAA IN xxx, udp 43 false f12" SERVFAIL qr,aa,rd,ra 43 0.0000447s

so add an option to customize it

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 3 lines in your changes missing coverage. Please review.

Project coverage is 81.75%. Comparing base (54ceade) to head (ac93088).
Report is 47 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/provisioner/controller/gatewayclass.go	40.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6699      +/-   ##
==========================================
- Coverage   81.76%   81.75%   -0.01%     
==========================================
  Files         133      133              
  Lines       15944    15953       +9     
==========================================
+ Hits        13037    13043       +6     
- Misses       2614     2617       +3     
  Partials      293      293              

Files with missing lines	Coverage Δ
internal/provisioner/controller/gateway.go	59.40% <100.00%> (+0.34%)	⬆️
internal/provisioner/model/model.go	100.00% <100.00%> (ø)
...nternal/provisioner/objects/dataplane/dataplane.go	87.67% <100.00%> (+0.03%)	⬆️
internal/provisioner/controller/gatewayclass.go	70.35% <40.00%> (-0.79%)	⬇️

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack