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

bump k8s version in AKS due to 1.26 reaching EOL #891

Open
orfeas-k opened this issue May 8, 2024 · 2 comments · May be fixed by #892
Open

bump k8s version in AKS due to 1.26 reaching EOL #891

orfeas-k opened this issue May 8, 2024 · 2 comments · May be fixed by #892
Labels
enhancement New feature or request

Comments

@orfeas-k
Copy link
Contributor

orfeas-k commented May 8, 2024

Context

AKS moves fast with Kubernetes versions released https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions?tabs=azure-cli#aks-kubernetes-release-calendar. Thus, we need to follow in order to have the CI running. Currently, the CI is failing since 1.26 is not supported any more.

What needs to get done

Bump k8s version from 1.26 to 1.28 since it's the latest supported version in for CKF. Note that we could also do 1.29 since in #756 we evaluated that 1.29 is compatible with k8s.

Definition of Done

AKS workflows use 1.28 version

@orfeas-k orfeas-k added the enhancement New feature or request label May 8, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5648.

This message was autogenerated

@orfeas-k orfeas-k linked a pull request May 8, 2024 that will close this issue
@orfeas-k
Copy link
Contributor Author

orfeas-k commented May 9, 2024

Katib UAT fails but it failed previously as well #893
Training-operator UAT starts to failing after bumping k8s version #894

We need to investigate more

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.

1 participant