feat(admission controller): Add new webhook settings

[wdhif]

What does this PR do?

Add support for the new Cluster Agent Admission settings.

Motivation

Needed to support new Cluster Agent settings.

Minimum Agent Versions

Are there minimum versions of the Datadog Agent and/or Cluster Agent required?

• Cluster Agent: v7.59.0

Describe your test plan

Using the following settings:

  features:
    admissionController:
      enabled: true
      validation:
        enabled: false
      mutation:
        enabled: false

Make sure that the output of those commands is as follows:

➜ kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io -A
No resources found
➜ kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io -A
No resources found

Modify the setting with:

  features:
    admissionController:
      enabled: true
      validation:
        enabled: true
      mutation:
        enabled: true

Make sure that the output changes to:

➜ kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io -A
NAME              WEBHOOKS   AGE
datadog-webhook   0          45s
➜ kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io -A
NAME              WEBHOOKS   AGE
datadog-webhook   3          47s

Checklist

• PR has at least one valid label: bug, enhancement, refactoring, documentation, tooling, and/or dependencies
• PR has a milestone or the qa/skip-qa label

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 95.23810% with 2 lines in your changes missing coverage. Please review.

Project coverage is 48.80%. Comparing base (86c5b1d) to head (951e1f2).

Files with missing lines	Patch %	Lines
api/datadoghq/v2alpha1/datadogagent_default.go	80.00%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1461      +/-   ##
==========================================
+ Coverage   48.70%   48.80%   +0.10%     
==========================================
  Files         224      224              
  Lines       19852    19886      +34     
==========================================
+ Hits         9669     9706      +37     
+ Misses       9675     9673       -2     
+ Partials      508      507       -1     

Flag	Coverage Δ
unittests	48.80% <95.23%> (+0.10%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
api/datadoghq/v2alpha1/datadogagent_types.go	100.00% <ø> (ø)
api/datadoghq/v2alpha1/test/builder.go	92.20% <100.00%> (+0.19%)	⬆️
...atadogagent/feature/admissioncontroller/feature.go	80.88% <100.00%> (+1.35%)	⬆️
internal/controller/datadogagent/feature/types.go	26.92% <ø> (ø)
api/datadoghq/v2alpha1/datadogagent_default.go	90.65% <80.00%> (+0.90%)	⬆️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 86c5b1d...951e1f2. Read the comment docs.

[gabedos]

Curious. What are some potential future mutating and validation configurations (besides just enabled true/false) that could be used by the user?

[wdhif]

In the future I would like to relocate the mutate_unlabelled setting to the mutation section (while keeping backward compatibility) and also add a validate_unlabelled one for the validation.

[gabedos]

nit: why not add the validation and mutation bool at the end with the cws bool.

[wdhif]

I considered them to be more "important" as the other ones since they control the main Validation and Mutation functionality.