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

Start testing k8s 1.29 #486

Merged
merged 2 commits into from
Feb 6, 2024
Merged

Start testing k8s 1.29 #486

merged 2 commits into from
Feb 6, 2024

Conversation

danielhoherd
Copy link
Member

Description

  • Start testing k8s 1.29
  • Use metadata.yaml to define all circleci and pytest k8s versions, like we do in astronomer/astronomer (closes astronomer/issues#5979)
  • Bump some k8s versions to the latest available kind patch version
  • Move and refactor generate_circleci_config.py
  • Use git_root_dir in all build scripts instead of GIT_ROOT

Related Issues

Testing

These are all dev workflow changes. There are no product changes in here, so QA does not need to do anything. CI passing is enough.

Merging

Merge everywhere.

@danielhoherd danielhoherd requested a review from a team as a code owner February 5, 2024 23:39
@danielhoherd danielhoherd merged commit 5326a02 into master Feb 6, 2024
10 of 11 checks passed
@danielhoherd danielhoherd deleted the 6129-add-k8s-1-29 branch February 6, 2024 21:36
danielhoherd added a commit that referenced this pull request Feb 6, 2024
* Use metadata.yaml to define k8s versions.

* Start testing k8s 1.29.
danielhoherd added a commit that referenced this pull request Feb 6, 2024
* Use metadata.yaml to define k8s versions.

* Start testing k8s 1.29.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant