[WIP] CMP-4310 added dynamic TLS settings

[vickeybrown]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds support for dynamic TLS configuration from the OpenShift cluster
API server, making the security-profiles-operator respect cluster-wide TLS
policies instead of using hardcoded settings.

Key changes:

• Fetches TLS configuration (cipher suites, minimum TLS version) from the
  OpenShift APIServer resource at startup
• Respects the cluster's TLS adherence policy to determine whether to honor
  cluster TLS settings
• Implements a TLS profile watcher that triggers graceful operator shutdown
  when TLS configuration changes, allowing Kubernetes to restart the pod with
  updated settings

This aligns the security-profiles-operator with OpenShift's cluster-wide
security policies and enables centralized TLS management.

Which issue(s) this PR fixes:

Fixes CMP-4310

Does this PR have test?

N/A

Special notes for your reviewer:

• The operator now requires get, list, and watch permissions on
  config.openshift.io/apiservers resources (RBAC changes included in
  deploy/base/role.yaml)
  • When TLS configuration changes are detected, the operator performs a
    graceful shutdown expecting Kubernetes to restart the pod with the new
    configuration
  • HTTP/2 is disabled by default for security reasons
  • Falls back to safe defaults if the APIServer TLS profile cannot be fetched

Does this PR introduce a user-facing change?

The `--tls-min-version` flag has been removed from the
  security-profiles-operator. TLS configuration (minimum version and cipher     
  suites) is now dynamically fetched from the OpenShift cluster's APIServer
  resource and automatically updated when the cluster TLS policy changes. 

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vickeybrown
Once this PR has been reviewed and has the lgtm label, please assign jaormx 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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: vickeybrown / name: Vickey Brown (4c2334b)

[k8s-ci-robot]

Welcome @vickeybrown!

It looks like this is your first PR to kubernetes-sigs/security-profiles-operator 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/security-profiles-operator has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @vickeybrown. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 24.74%. Comparing base (11d77f4) to head (37ea514).
⚠️ Report is 1152 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #3190       +/-   ##
===========================================
- Coverage   45.50%   24.74%   -20.77%     
===========================================
  Files          79      128       +49     
  Lines        7782    17962    +10180     
===========================================
+ Hits         3541     4444      +903     
- Misses       4099    13223     +9124     
- Partials      142      295      +153     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.