security: update supported version

[rockwotj]

Backports Required

• none - not a bug fix
• none - this is a backport
• none - issue does not exist in previous branches
• none - papercut/not impactful enough to backport
• v23.3.x
• v23.2.x
• v23.1.x

Release Notes

• none

[michael-redpanda]

I wonder if it would make sense to list the versions expected EoL and when previous versions went EoL.

[d3k4z]

For sure it will not hurt, and it is security related so folks will appreciate.

[d3k4z]

@michael-redpanda I've improved the policy and added details. I've checked some other repositories, and I couldn't identify any EOL announcements. But nevertheless, I would love to see this information somewhere. @wreet do you agree?

[michael-redpanda]

Added @d3k4z and @wreet

This file is pretty old and has, obviously, not been kept up-to-date. I think we should figure out if

1. we keep it
2. what it should contain
3. what this looks like on backport branches

[vbotbuildovich]

new failures in https://buildkite.com/redpanda/redpanda/builds/43485#018cda88-29dc-4116-86f2-9c5531381c4e:

"rptest.tests.recovery_mode_test.DisablingPartitionsTest.test_disable"

new failures in https://buildkite.com/redpanda/redpanda/builds/43565#018cea02-7119-4e8f-a1ad-b4ffd7bd083c:

"rptest.tests.nodes_decommissioning_test.NodeDecommissionFailureReportingTest.test_allocation_failure_reporting"

new failures in https://buildkite.com/redpanda/redpanda/builds/43601#018cef2d-188d-4e3c-abee-f6baac4df0d9:

"rptest.tests.cloud_storage_timing_stress_test.CloudStorageTimingStressTest.test_cloud_storage.cleanup_policy=delete"

[vbotbuildovich]

ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/43485#018cda88-29dc-4116-86f2-9c5531381c4e

ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/43565#018cea2b-e227-415f-8a88-9a3c77abf0e3

[d3k4z]

lgtm!

[d3k4z]

We would need to add a reference to our Redpanda Security Policy. Something in the spirit of:

Official Redpanda Security Policy can be found on redpanda.com/security

[d3k4z]

@michael-redpanda I've improved the policy and added details. I've checked some other repositories, and I couldn't identify any EOL announcements. But nevertheless, I would love to see this information somewhere. @wreet do you agree?

[rockwotj]

Updated with EOL info

[d3k4z]

lgtm!

[piyushredpanda]

@mattschumpert are the EoL dates confirmed/lgtm to you? Rest, LGTM.

[mattschumpert]

They look about right. I trust these are the GA bits available dates and you've verified them @piyushredpanda

Is this going in the codebase? That sounds a bit risky cause EOL dates can change (e.g. we pushed 22.3 EOL out a month)