Skip to content
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

Container Teleportation #418

Closed
SteveLasker opened this issue Jun 23, 2020 · 8 comments
Closed

Container Teleportation #418

SteveLasker opened this issue Jun 23, 2020 · 8 comments
Assignees

Comments

@SteveLasker
Copy link
Contributor

The ability to run any container on any service within azure, as if the image was pre-cached will unlock many additional possibilities.

https://aka.ms/acr/teleport

@SteveLasker SteveLasker created this issue from a note in Backlog - Archived (In Progress) Jun 23, 2020
@scp-mb
Copy link

scp-mb commented Jun 14, 2021

To provide a real world use case, currently we are using AKS to spin up new containers running Azure DevOps agents to handle CI/CD jobs, which teardown after each completed job. Only two agent containers are running 24/7 to meet immediate demand with the rest spun up on demand as the agent pool queue increases.

Currently, that means we're using auto scaling to spin up additional VM nodes as load increases, however using ACI through virtual nodes is pretty much a perfect use case for this as the containers are often very short lived. The downside to this is with our agent image hosted in ACR it's somewhere in the region of ~6.5GB, which is causing it to take 5-10 minutes to spin up new containers which is unfortunately completely unusable for this use case.

@huzefaqubbawala
Copy link

Hi Steve,

Currently we are using ACI to launch the containers on the fly to do some long running operations. ACI is great technology it allows us to run our workload in serverless fashion.

The only pain area is the pull time of the image. We use azure container registry and are in the same region then also it takes whopping 120 seconds for 1.8GB image to start.

Can we please get an update on when project teleport will be made available for Azure Container Instances (ACI)

@fschmied
Copy link

@SteveLasker Can you maybe give us an update on the status of Project Teleport? On the Internet, I can only find your blog post from 2019. On the Project Teleport readme page, I can see you're currently in "Preview 2", which focuses on AKS, but could you maybe give us an idea of your estimated timeline?

Specifically, I'm interested in:

  • When might Windows images be supported? Those are notoriously large (measured in GB), so they are the most likely to profit from this feature.
  • When might the AKS integration come out of private preview?

@terencet-dev
Copy link
Contributor

Hi, everyone!

Wanted to provide an update that this project is actively funded and and working on the developments for Project Teleport. In terms of timeline, we are targeting Linux support this year.

@jrauschenbusch
Copy link

@terencet-dev Is there any milestone planning? I mean is the ACR implementation already finished or is this also still ongoing? And how about the AKS integration. Currently it seems that this is a private preview. There is also a ticket in the AKS Roadmap for now quite a long time which is still "in progress", but unfortunately no updates there...(see Azure/AKS#1785)

@terencet-dev
Copy link
Contributor

Hi @jrauschenbusch, thanks for reaching out. The implementation is still underway and are targeting for an announcement later this year. We can provide more updates as we enter Q3 of this year. Thanks!

@jrauschenbusch
Copy link

@terencet-dev Any status updates?

@sajayantony
Copy link
Contributor

Previewed - https://learn.microsoft.com/en-us/azure/container-registry/tutorial-artifact-streaming

Backlog - Archived automation moved this from In Progress to Done (GA) Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Public Preview (Shipped & Improving)
Development

No branches or pull requests

8 participants