Reuse container images across environments by default

Open
#77 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker
Domain
devops, infrastructure

Research direction

Start with the linked image-mirroring documentation for the current deployment flow. The issue does not name repository files or tests; done means the same image name and tag is mirrored only once across all environments, reducing deployment time.

Written by the indexing model from the issue text.

Description

status: later

When deploying an application from a container image, we have a mirroring process copying the image on the image registry attached to the cluster (more information here [https://hub.qovery.com/docs/using-qovery/deployment/image-mirroring/#application-deployed-from-a-container-registry])

we will improve this part and ensure we mirror only once the same image name / tag across all the environments, speeding up the deployment time

Votes: 3 | Submitted: 2024-10-08 | Featurebase: https://roadmap.qovery.com/p/reuse-container-images-across-environments | Author: Alessandro Carrano

Dominant language
No language data
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Qovery/Roadmap

All issues in Qovery/Roadmap

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.