Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with Kubernetes version 1.28 #15765

Closed
louiscb opened this issue Oct 2, 2023 · 1 comment · Fixed by #15766
Closed

Compatibility with Kubernetes version 1.28 #15765

louiscb opened this issue Oct 2, 2023 · 1 comment · Fixed by #15766
Labels
enhancement New feature or request

Comments

@louiscb
Copy link

louiscb commented Oct 2, 2023

Summary

The latest version of Kubernetes is 1.28. In the Argocd docs the highest compatible and tested version is 1.27. See link here -> https://argo-cd.readthedocs.io/en/stable/operator-manual/installation/#tested-versions

Motivation

Argo is currently running in a cluster of ours that is on v1.27 and we would like to upgrade the cluster to v1.28, however we are unsure if this will break any functionality in argo.

Proposal

Test Argo on Kubernetes v1.28, fix and publish any related issues, include v1.28 in the list of tested Kubernetes versions.

@vini-intenseye
Copy link

Does the latest version work well with 1.28? I am having issues with installing 2.10.x on GKE 1.28.

Failed to load live state: failed to get cluster info for "https://kubernetes.default.svc/": error synchronizing cache state : error getting openapi resources: the server is currently unable to handle the request
Failed to load target state: failed to get cluster version for cluster "https://kubernetes.default.svc/": failed to get cluster info for "https://kubernetes.default.svc/": error synchronizing cache state : error getting openapi resources: the server is currently unable to handle the request
error synchronizing cache state : error getting openapi resources: the server is currently unable to handle the request

Any ideas here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants