Chris Seto

Closing this as "won't do" as I don't think the issue is valid anymore given all our learnings from Travis Downs 😓

Locking scope of this issue to the listed tasks with a target date of May 13th just to have a date that should be achievable.

I'm going to close this out as done as it's primarily an epic of epics at this point.

@alejandroEsc @JakeSCahill I think we can close this out as done?

Here's an example of a _great_ known issue/limitation candidate: https://github.com/redpanda-data/helm-charts/issues/1173

I like `known-issue`! We can even use the same color. Though we should probably document somewhere what it means.

Suggestion from @tmgstevens: we should probably aim to support 4 Kubernetes versions each for a period of 12 months as is common with upstream Kubernetes. Could we get to a...

The biggest blocker to testing against EKS, GKE, AKS, OpenShift, and Rancher is the need to support the infrastructure that creates those clusters. We don't have the bandwidth right now...

> We should probably just stick to 3 versions imho, and probably follow eks or use a min supported model among the cloud providers and try not to lag too...

I've re-wrapped the error messages from Camilo: ``` { "level": "debug", "ts": "2024-04-01T21:32:22.924Z", "logger": "events", "msg": "Helm upgrade failed for release redpanda/redpanda with chart [email protected]: failed to create resource: Service...