You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am preparing for a round of cluster upgrades and I'm trying to understand what Kubernetes versions (1.27+) Argo Events supports.
Describe the solution you'd like
A table like the one provided by Argo Workflows, clearly stating AE vs k8s version compatibility.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
+1 for a k8s compatibility table. We have deferred upgrading our cluster for this reason, and are starting to incur costs due to the lack of upgrades, so I started digging to find an answer.
no it doesn't mean that, an argoworkflows version that has api version of 0.24 (https://github.com/argoproj/argo-workflows/blob/v3.4.11/go.mod#L64) still runs fine on my 1.29 cluster. i'm sure 1.31 cluster will handle current argo-events just fine, upgrade your cluster!
In addition to k8s version compatibility, I think maybe we also need to include argo-workflow version in the matrix since argo-events should be coupled with argo-workflow.
It's can easily be verified through code, but I think it's can be added into both operation manual.
Is your feature request related to a problem? Please describe.
I am preparing for a round of cluster upgrades and I'm trying to understand what Kubernetes versions (1.27+) Argo Events supports.
Describe the solution you'd like
A table like the one provided by Argo Workflows, clearly stating AE vs k8s version compatibility.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This feature request is identical to argoproj/argo-workflows#8198 and argoproj/argo-cd#12276.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: