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

chore: fetch Envoy from Github artifacts #5329

Merged

Conversation

jakubdyszkiewicz
Copy link
Contributor

@jakubdyszkiewicz jakubdyszkiewicz commented Nov 16, 2022

I uploaded Envoy binaries here https://github.com/kumahq/envoy-builds/releases/tag/v1.22.1 following the convention specified here https://github.com/425devon/envoy-builds/blob/cd16b3e388ee8fa167b17b44c421226484d779f6/.github/workflows/ci_amd.yaml#L249-L259

Binaries in tars in envoy-builds are simple envoy-alpine, envoy-darwin etc. I think it's useful to still use the version in Envoy binary name in Kuma build directory. This way if code changes the version and you still have old binary, we will fetch the new one. Either way, in the package for end user, it has just envoy.

I simplified distros.sh to just use binaries fetched using Make.

fix #5269

Checklist prior to review

  • Link to docs PR or issue --
  • Link to UI issue or PR --
  • Is the issue worked on linked? --
  • The PR does not hardcode values that might break projects that depend on kuma (e.g. "kumahq" as a image registry) --
  • The PR will work for both Linux and Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
  • Unit Tests --
  • E2E Tests --
  • Manual Universal Tests --
  • Manual Kubernetes Tests --
  • Do you need to update UPGRADE.md? --
  • Does it need to be backported according to the backporting policy? --
  • Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?

Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
@jakubdyszkiewicz jakubdyszkiewicz requested a review from a team as a code owner November 16, 2022 08:31
tools/envoy/fetch.sh Outdated Show resolved Hide resolved
Copy link
Contributor

@bartsmykla bartsmykla left a comment

Choose a reason for hiding this comment

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

overall lgtm, just two questions/suggestions

bartsmykla and others added 2 commits November 16, 2022 10:26
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
@jakubdyszkiewicz jakubdyszkiewicz merged commit 8198e76 into kumahq:master Nov 16, 2022
@jakubdyszkiewicz jakubdyszkiewicz deleted the ci/envoy-github-artifacts branch November 16, 2022 15:53
@lahabana lahabana mentioned this pull request Dec 13, 2022
@bartsmykla
Copy link
Contributor

@Mergifyio backport release-2.0

@mergify
Copy link
Contributor

mergify bot commented Mar 8, 2023

backport release-2.0

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Mar 8, 2023
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
(cherry picked from commit 8198e76)

# Conflicts:
#	mk/envoy.mk
#	tools/releases/distros.sh
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.

Move envoy binaries to kumahq/envoy-builds
3 participants