You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Etcd publishes multi-arch along with arch specific images, i.e:
Now that multi-arch image manifests are mature and widely adopted should we stop creating and pushing single arch images?
We would need to consider how much lead time to give for this change and how we communicate this to folks that might be consuming the single arch image tags currently.
Why is this needed?
For the project this would simplify scripts/release.sh and scripts/test_images.sh and cut some time from the release process. For downstream users this would make the image landscape for etcd much simpler to consume.
The text was updated successfully, but these errors were encountered:
From the discussion in #15270 it sounds like there might be agreement to go ahead with this feature. I've created #15605 but left in draft because I think this still needs wider discussion, particularly on when it would be ok to make this change and what steps we should take to communicate it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.
What would you like to be added?
Currently Etcd publishes multi-arch along with arch specific images, i.e:
Now that multi-arch image manifests are mature and widely adopted should we stop creating and pushing single arch images?
We would need to consider how much lead time to give for this change and how we communicate this to folks that might be consuming the single arch image tags currently.
Why is this needed?
For the project this would simplify
scripts/release.sh
andscripts/test_images.sh
and cut some time from the release process. For downstream users this would make the image landscape for etcd much simpler to consume.The text was updated successfully, but these errors were encountered: