feat(fips): disable kvm module in fips mode

[kruskall]

Proposed commit message

go-libvirt is pulling quite a few x/crypto packages

disable kvm modules in fips mode

should remove the following packages from metricbeat:

• golang.org/x/crypto/chacha20
• golang.org/x/crypto/curve25519
• golang.org/x/crypto/ssh
• golang.org/x/crypto/internal/poly1305

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[simitt]

With these changes, I wonder whether it really still makes sense to keep the metricbeat/module/kvm enabled for FIPS mode when metricbeat/module/kvm/status and metricbeat/module/kvm/dommemstat are disabled? While the third party libraries in question are removed in this PR, functionality wise I don't see the point in keeping the kvm module enabled.

Other than that, LGTM

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[mauri870]

Reviewed the code, LGTM.

[kruskall]

With these changes, I wonder whether it really still makes sense to keep the metricbeat/module/kvm enabled for FIPS mode when metricbeat/module/kvm/status and metricbeat/module/kvm/dommemstat are disabled? While the third party libraries in question are removed in this PR, functionality wise I don't see the point in keeping the kvm module enabled.

kvm does not add a metricset, only an asset so there's no impact but I guess we could disable it too