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

Align k8s version across ci distributions #784

Open
noahpb opened this issue Sep 19, 2024 · 0 comments
Open

Align k8s version across ci distributions #784

noahpb opened this issue Sep 19, 2024 · 0 comments
Labels
ci Issues pertaining to CI / Pipelines / Testing enhancement New feature or request

Comments

@noahpb
Copy link
Contributor

noahpb commented Sep 19, 2024

We are implementing nightly tests of uds-core against multiple k8s distributions. Currently, the IaC for these environments are managed independently with different tools (tofu, eksctl, uds-k3d). Since we manually declare the k8s version for each distribution in its IaC, it's difficult to determine which version we're using across the different distros in CI without digging into logs or pipeline code.

We should ensure that we are using the same k8s version across distributions. A system for tracking and updating these versions should be documented and/or automated. When looking at a pipeline run, it should be easy to tell what version and k8s distribution was used.

Solution

Open to ideas here - at a minimum we should have documentation for where the k8s version is declared for each distro and document the process for updating. As part of #777, we can display what version was used in the dashboard.

Additional context

We should also determine when a version update is required.

@noahpb noahpb added enhancement New feature or request ci Issues pertaining to CI / Pipelines / Testing labels Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Issues pertaining to CI / Pipelines / Testing enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant