Sorry if this isn't the right repo for this type of issue. Hoping it is :crossed_fingers:
I noticed that for the redis-operator images you're building latest for amd64, then building separate images for arm-64 support. Unless I'm mistaken, a better way to build for multiple architectures is to just tag them the same and upload multiple versions to the same registry under the same tag. Most registries will handle this automatically.
Each of their images supports 5 different architectures for the same tag, which means I can tell Karpenter to use either amd64 or arm64 for the same image tag and not run into problems.
Would you be open to implementing this for the redis-operator and redis images?
Hi :slightly_smiling_face:
Sorry if this isn't the right repo for this type of issue. Hoping it is :crossed_fingers:
I noticed that for the redis-operator images you're building
latest
for amd64, then building separate images for arm-64 support. Unless I'm mistaken, a better way to build for multiple architectures is to just tag them the same and upload multiple versions to the same registry under the same tag. Most registries will handle this automatically.For an example, see the cert-manager images:
Each of their images supports 5 different architectures for the same tag, which means I can tell Karpenter to use either
amd64
orarm64
for the same image tag and not run into problems.Would you be open to implementing this for the redis-operator and redis images?