-
Notifications
You must be signed in to change notification settings - Fork 716
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
Comments
@jsanz is there are reason we can't have a multi-architecture image with both |
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:
^ note that |
Sorry for the unexpected changes, we initially enabled ARM only for With the latest changes we should have the following builds:
@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 |
@pebrc I see latest
|
@jsanz our e2e tests succeeded last night 👍 |
Nice! |
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:docker.elastic.co/elastic-maps-service/elastic-maps-server-ubi8:8.15.0
docker.elastic.co/elastic-maps-service/elastic-maps-server-ubi:8.15.0
docker.elastic.co/elastic-maps-service/elastic-maps-server:8.15.0-amd64
The text was updated successfully, but these errors were encountered: