Eric Bariaux
Eric Bariaux
See section Running custom project in README.md under kubernetes Although issue talks about local k8s, the mechanism also works for deployment in cloud environments.
As of June 2025, Image Volumes under kubernetes is now a beta feature (still disabled by default)
Still a beta, disabled by default, in k8s 1.33 in Aug 2025
Thanks @pankalog For Balena, I'll just remove the requirements. As for the choice of registry, we're going with AWS ECR. I'm not interested in self-hosting a registry (I've done it...
As a first step, I'm looking into the details of ECR and will propose an "architecture / configuration" in this ticket on how to move foward.
Each AWS account has a private default registry at .dkr.ecr..amazonaws.com For each docker image you want to push (multiple tags per image are OK), you need to create a repository...
Older April 2021 deleted after validation with @aktur
I don't think there is much more to do for this issue. I would propose to: - use the ECR in our developers account - create a repository for each...
I have now added lifecycle policies to the existing repositories and created the documentation in https://docs.google.com/document/d/1Xkz-1zehcGPrq1GenhRd_l3n5Pae_dJnOLBMoXYnf3c/edit?pli=1&tab=t.0#heading=h.1fob9te
@wborn You can but I think you need AWS CLI installed aws ecr get-login-password --region | docker login --username AWS --password-stdin .dkr.ecr..[amazonaws.com](http://amazonaws.com/)