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.

Sign up for GitHub

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

Jump to bottom

chore: Update setup E2E to match latest Knative release #2189

Merged
merged 1 commit into from
Feb 28, 2024
Merged

chore: Update setup E2E to match latest Knative release #2189

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions hack/allocate.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,13 +25,13 @@ export TERM="${TERM:-dumb}"

main() {

local knative_serving_version=v1.10.1
local knative_eventing_version=v1.10.1
local contour_version=v1.10.0
local knative_serving_version=v1.13.0
local knative_eventing_version=v1.13.0
local contour_version=v1.13.0
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not sure if there's any benefit to test with Contour as networking-layer for Serving. I'd switch to Kourier if possible. In a follow-up PR.


# Kubernetes Version node image per Kind releases (full hash is suggested):
# https://github.com/kubernetes-sigs/kind/releases
local kind_node_version=v1.27.1@sha256:b7d12ed662b873bd8510879c1846e87c7e676a79fefc93e17b2a52989d3ff42b
local kind_node_version=v1.29.2@sha256:51a1434a5397193442f0be2a297b488b6c919ce8a3931be0ce822606ea5ca245
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I assume it's locking kind on certain kube version. But we lock kind binary on certain release version anyway. I wonder if their default isn't enough. At least for current release it matches 1.29.2.


# shellcheck disable=SC2155
local em=$(tput bold)$(tput setaf 2)
Expand Down
6 changes: 3 additions & 3 deletions hack/binaries.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,12 @@ set -o pipefail
export TERM="${TERM:-dumb}"

main() {
local kubectl_version=v1.27.2
local kind_version=v0.19.0
local kubectl_version=v1.29.2
local kind_version=v0.22.0
local dapr_version=v1.11.0
local helm_version=v3.12.0
local stern_version=1.25.0
local kn_version=v1.12.0
local kn_version=v1.13.0

local em=$(tput bold)$(tput setaf 2)
local me=$(tput sgr0)
Expand Down
Loading