Goodbye Azure Kubernetes Service! Hello Azure Container Apps! - Johnny Hooyberghs
Вставка
- Опубліковано 2 тра 2024
- This talk was recorded at NDC London in London, England. #ndclondon #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
ndcconferences.com
ndclondon.com/
Subscribe to our UA-cam channel and learn every day:
/@NDC
Follow our Social Media!
/ ndcconferences
/ ndc_conferences
/ ndc_conferences
#azure #kubernetes #cloud #dotnet #microsoft #serverless
You have decided to run your cloud-native applications using containers. But how will you deploy these containers to Azure Cloud?
AKS or Azure Kubernetes Service is very popular, but it also adds a lot of complexity to setting up and deploying your infrastructure!
ACA or Azure Container Apps are Microsoft Azure's new serverless container offering, built as an abstraction on top of AKS, and could be the solution to your question!
In this session, I will introduce you to Azure Container Apps for .NET 8 and guide you through setting up a multi-container app using Azure Container App container environments. - Наука та технологія
Sure! Here's the corrected version:
Thanks, this is exactly what I was searching for.
Can you selectively only call revision #1 of an app and not #2? This would be helpful to build apps for each pull request for example where revision #1 is staging, and revision #2 is the PR
When you create a new revision, you can optionally add a suffix. Each revision has its own URL (if you are using Ingress), including this suffix. The URL for a specific revision can be found in its details. So, the answer to your question would be yes.
Container app cold start is still an issue atm.
True, takes up to 20 seconds to go from 0 to 1. Too much to have it scale to 0 on a production environment.
you can left 1 instance to be aways available so it could not have the issue with the cold start
@@stefancfefo yeah but then you will have to pay for inactive rates which is wastage especially for a grunty vm.