✨ Add TLS configuration flags for CAPM3

[as20203]

Added tls configuration flags for CAPM3.

This enables flags --tls-min-version and --tls-max-version flags, which can be used to limit TLS versions server accepts. Choices are TLS12 and TLS13, so you can force TLS 1.2 only, TLS 1.3 only, or (default) TLS 1.2 and TLS 1.3 is negotiated between server and client.

This also disables TLS 1.0 and TLS 1.1 as they're insecure and obsolete and not supported by Go TLS library.

[as20203]

/hold

[tuminoid]

Metal3 authors again.

Also the whole header looks to be formatted funny.

[tuminoid]

Building manager and running ./bin/manager --help says:

  -tls-max-version string
    	The maximum TLS version in use by the webhook server.
    	Possible values are VersionTLS10, VersionTLS11, VersionTLS12, VersionTLS13. (default "VersionTLS13")
  -tls-min-version string
    	The minimum TLS version in use by the webhook server.
    	Possible values are VersionTLS10, VersionTLS11, VersionTLS12, VersionTLS13. (default "VersionTLS12")

We are not supporting TLS 1.0 or TLS 1.1.

[as20203]

/test-centos-e2e-integration-main

[as20203]

/test-ubuntu-integration-main

[as20203]

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

[tuminoid]

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

[tuminoid]

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

[tuminoid]

/lgtm

[tuminoid]

/unhold
/assign @mboukhalfa @lentzi90

[lentzi90]

/approve

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90, tuminoid

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lentzi90]

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

[tuminoid]

/cherry-pick release-1.4

[ghost]

@tuminoid: #1041 failed to apply on top of branch "release-1.4":

Applying: Added tls configuration flags for CAPM3.
Using index info to reconstruct a base tree...
M	main.go
Falling back to patching base and 3-way merge...
Auto-merging main.go
CONFLICT (content): Merge conflict in main.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Added tls configuration flags for CAPM3.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.4

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/test-infra repository.