Remove cloud-defend from agent

[mjwolf]

What does this PR do?

cloud-defend (a.k.a. Defend for Containers) will be removed from the next major release. This removes cloud-defend from agent, by removing it from packaging scripts and template kubernetes files.

Why is it important?

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/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

Defend for Containers never left beta, so although removing it could be disruptive to users of the integration, it's acceptable to be a breaking change in a major update.

How to test this PR locally

After building the agent package, inspect it to ensure the cloud-defend package is not included in it, and the cloud-defend executable isn't on the system after installing the agent.

[cmacknz]

Thanks! I'll hold on approving this until main has cut over to 9.0 so this doesn't accidentally ship in 8.16.

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.

[blakerouse]

Looks good.

[jlind23]

@cmacknz now that main became 9.0 can we make it land?

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[mbudge]

We we're planning on using Cloud Defend for Containers this year. Is this been moved to another agent or is it totally depreciated?

[nick-alayil]

@mbudge

is it totally depreciated?

Yes, Defend for Containers (D4C) has been deprecated from serverless and Elastic Stack / ECH 9.0.0. D4C will remain available in the 8.x stack as beta. While D4C is being sunset, we're actively in the process of building a new SIEM aligned k8s security solution. IIRC, you're planning to use Azure Red Hat OpenShift, I'd welcome the opportunity to schedule a call to discuss the following:

• Strategic reasoning behind this decision
• Technical considerations that led to D4C deprecation
• Our future direction for k8s security
• Your specific k8s security reqs and use cases
• How our new solution can address your needs
• Potential interim solutions using our current capabilities

I'll reach out to you to find a time that works best for this discussion.