Skip to content

chore: upgrade k8s for CI, only keeping supported versions #1657

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

Merged
merged 1 commit into from
Sep 4, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/e2e-test.yml
Original file line number Diff line number Diff line change
@@ -32,8 +32,8 @@ jobs:
- name: Setup Minikube-Kubernetes
uses: manusa/[email protected]
with:
minikube version: v1.28.0
kubernetes version: v1.25.5
minikube version: v1.31.2
kubernetes version: v1.28.1
github token: ${{ secrets.GITHUB_TOKEN }}
driver: docker

2 changes: 1 addition & 1 deletion .github/workflows/integration-tests.yml
Original file line number Diff line number Diff line change
@@ -36,7 +36,7 @@ jobs:
- name: Set up Minikube
uses: manusa/[email protected]
with:
minikube version: 'v1.28.0'
minikube version: v1.31.2
kubernetes version: ${{ inputs.kube-version }}
driver: 'docker'
github token: ${{ secrets.GITHUB_TOKEN }}
6 changes: 3 additions & 3 deletions .github/workflows/pr.yml
Original file line number Diff line number Diff line change
@@ -35,20 +35,20 @@ jobs:
strategy:
matrix:
java: [ 11, 17 ]
kubernetes: [ 'v1.23.15', 'v1.24.9', 'v1.25.5' ]
kubernetes: [ 'v1.25.13', 'v1.26.8', 'v1.27.5', 'v1.28.1' ]
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I guess we're dropping older versions completely?

Copy link
Collaborator

@csviri csviri Aug 25, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's a good quesiton, before we said (if ai remember correctly, that we will test on supported versions only), but not sure we also say that we will support last n major versions. That might be a better strategy in practice. What do you think?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that this will increase the CI run time. We could test older versions on main maybe once a day instead of on each PR?

Copy link
Collaborator

@csviri csviri Aug 25, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it's always a compromise, a shorter build is always better, maybe optimize that when we see that it is too long, not sure if it will be.
It depends also how much of those version we want to run, maybe always the last 6 major versions?

uses: ./.github/workflows/integration-tests.yml
with:
java-version: ${{ matrix.java }}
kube-version: ${{ matrix.kubernetes }}

httpclient-tests:
strategy:
matrix:
httpclient: [ 'vertx', 'jdk', 'jetty' ]
uses: ./.github/workflows/integration-tests.yml
with:
java-version: 17
kube-version: 'v1.25.5'
kube-version: 'v1.28.1'
http-client: ${{ matrix.httpclient }}
experimental: true