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

Switch from keda build-tools image to keda-tools image #218

Merged
merged 4 commits into from
Feb 20, 2024

Conversation

joelsmith
Copy link
Contributor

@joelsmith joelsmith commented Feb 20, 2024

Several changes related to builds and the release process, plus a bonus, unrelated docs fix:

  • Switch from keda build-tools image to keda-tools image since the KEDA build-tools image is no longer being updated and the keda-tools image replaces it.
  • have hacks/relprep.sh detect and use the same version of k8s libraries as KEDA is using, for a given version (See Bump Go deps to be in sync with KEDA 2.13.0 (use the same k8s version) #215 )
  • fix new CSV comparison check by running it later in the process so that the comparison will be valid.
  • Clean up the examples of omitStages to be a list, not string

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO)

Fixes #215

Signed-off-by: Joel Smith <[email protected]>
Copy link
Contributor

@jkyros jkyros left a comment

Choose a reason for hiding this comment

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

Looks good, just one question and a comment.

hack/relprep.sh Outdated Show resolved Hide resolved
done

# hack: force version of openshift API module based upon k8s->openshift version skew (e.g. 1.27 -> 4.14)
openshift_branch="release-4.$(($(echo $k8sver | sed 's/v0\.\([0-9]*\)\.[0-9]*$/\1/')-13))"
Copy link
Contributor

Choose a reason for hiding this comment

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

I've always wished there was a canonical file somewhere in github that had the openshift:kube version mapping, but I don't know of one either. I think -13 (or +2.87 ) is reasonable for now as long as it holds and we can get away with it -- I'd rather do that than maintain our own mapping table here and adding the new version every time we do the release.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay, thanks for being a sounding board on this. I think I'm leaning in the same direction. Probably once it breaks, we'll notice when we try to build with an incompatibly-skewed version, and that can be our cue to fix the skew magic number.

@jkyros
Copy link
Contributor

jkyros commented Feb 20, 2024

/lgtm

@joelsmith joelsmith merged commit 903e520 into kedacore:main Feb 20, 2024
5 checks passed
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.

Bump Go deps to be in sync with KEDA 2.13.0 (use the same k8s version)
2 participants