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

Update Elastic Maps Server image #8034

Closed
jsanz opened this issue Aug 29, 2024 · 6 comments · Fixed by #8085
Closed

Update Elastic Maps Server image #8034

jsanz opened this issue Aug 29, 2024 · 6 comments · Fixed by #8085
Assignees
Labels
>enhancement Enhancement of existing functionality v2.15.0

Comments

@jsanz
Copy link
Member

jsanz commented Aug 29, 2024

EMS started to publish additional docker images based on the hardened chainguard-base docker image in 8.14. We don't plan to deprecate the -ubi images, but upgrade to -ubi9 soon but it would be great for ECK users to migrate to the Chainguard base images by default.

For example, for 8.15.0 we have:

  • UBI8 image at docker.elastic.co/elastic-maps-service/elastic-maps-server-ubi8:8.15.0
  • Aliased UBI image at docker.elastic.co/elastic-maps-service/elastic-maps-server-ubi:8.15.0
  • New chainguard image at docker.elastic.co/elastic-maps-service/elastic-maps-server:8.15.0-amd64
@botelastic botelastic bot added the triage label Aug 29, 2024
@pebrc pebrc added the >enhancement Enhancement of existing functionality label Aug 29, 2024
@botelastic botelastic bot removed the triage label Aug 29, 2024
@pebrc pebrc added the v2.15.0 label Aug 29, 2024
@pebrc
Copy link
Collaborator

pebrc commented Sep 30, 2024

New chainguard image at docker.elastic.co/elastic-maps-service/elastic-maps-server:8.15.0-amd64

@jsanz is there are reason we can't have a multi-architecture image with both arm64 and amd64 behind a shared tag e.g. 8.16.0 ?

@pebrc
Copy link
Collaborator

pebrc commented Sep 30, 2024

Discussed out of band: we should have a multi-arch image for 8.16.0-SNAPSHOT very soon. That means as part of this task we should also remove the restriction on running the e2e tests for both archictures which is currently done via build tags:

E2E_TAGS: "es,kb,apm,ent,beat,agent"

^ note that ems is missing from the list above on ARM

@jsanz
Copy link
Member Author

jsanz commented Sep 30, 2024

Sorry for the unexpected changes, we initially enabled ARM only for master but by the end of last we we also did it to 8.x, my fault for not updating this issue before 😓

With the latest changes we should have the following builds:

  • 7.17: amd64 only
    • elastic-maps-server-ubi (based on UBI8)
  • 8.15: amd64 only
    • elastic-maps-server-ubi (based on UBI8)
    • elastic-maps-server (based on wolfi)
  • 8.16 and later: amd64 and arm64
    • elastic-maps-server-ubi (based on UBI9)
    • elastic-maps-server (based on wolfi)
  • 9.0 and later: amd64 and arm64
    • elastic-maps-server-ubi (based on UBI9)
    • elastic-maps-server (based on wolfi)

@jmlrt may keep me honest here, but in case this makes things easier to manage on your end I'd like to add we are also starting to support an alias for wolfi images. Checking the code in the unified release, this will be only the case for 8.16 and later (branches main and 8.x).

@jsanz
Copy link
Member Author

jsanz commented Oct 1, 2024

@pebrc
Copy link
Collaborator

pebrc commented Oct 2, 2024

@jsanz our e2e tests succeeded last night 👍

@jsanz
Copy link
Member Author

jsanz commented Oct 2, 2024

Nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality v2.15.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants