Manage Container Images in Azure Container Registry Flashcards
1
Q
What does ACR enable?
A
- build on demand or fully automate builds with triggers such as source commits and base image updates
- pull images from an azure container registry to various deployment targets (kubernetes, app service etc)
- can be pushed to as part of container dev workflow by being targetted from a CI tool
- ACR tasks can auto rebuild app images when base image updated or automate image builds when team commits code to git repo
2
Q
What are ACR tiers (generally)?
A
- ACR is available in multiple tiers, each one providing predictable pricing and several options for aligning to the capacity and usage patterns of your private Docker reg in azure
- all benefit from advanced azure storage features
3
Q
What is the basic tier of ACR?
A
- cost optimised entry point for devs learning about ACR
- registers have same programmatic capabilities as Standard and Premium
- however storage and image throughput are appropriate for lower usage scenarios
4
Q
What is the standard tier of ACR?
A
- same capabiltiies as basic but with increased storage and image throughput
- standard registries should satisfy needs of most prod scenarios
5
Q
What is premium tier of ACR?
A
- Provide the highest amount of storage and concurrent operations
- enables high volume scenarios
also adds features such as geo-replication for managing a single registry across multiple regions, content trust for image tag singing and private link with private endpoints to restrict access
6
Q
What is an image in ACR and what else can ACR store?
A
- read-only snapshot of a docker compatible container
- ACRs can include both Windows and Linux images
- in addition to docker container images ACR stores related content formats such as Helm charts and images built to the Open Container Initiative image format specificationW
7
Q
What are ACR tasks best used for?
A
- to streamline building, testing, pushing and deploying images in Azure
- configure build tasks to automate your container OS and framework patching pipeline, and build images automatically when your team commits code to source control
8
Q
What is Encryption at rest in terms of ACR?
A
- All container images in your reg are encrypted at rest
- azure auto encrypts image before storing it, and decrypts it on the fly when you or your app and services pull the image
9
Q
What is Regional storage in terms of ACR?
A
- ACR stores data in the region where the reg is created to help meet data residency and compliance requirements
- in all regions bar Brazil south and Southeast Asia Azure may also store reg data in a paired region in the same geo
- if regional outage occurs the reg data may become unavailable and isn’t auto recovered
- customers who want to have better data protection should enable geo-replication
10
Q
What is Zone redundancy in terms of ACR?
A
- a feature of premium tier
- use availability zones to replicate your reg to a min of 3 separate zones in each enabled region
11
Q
What is scalable storage in terms of ACR?
A
- ACR allows you to create as many repos, images or layers or tags as you need up to reg storage limit
- high numbers of repos and tags can impact the performance of reg
- should delete un-used ones periodically
12
Q
What are ACR tasks?
A
- suite of features within ACR that provides cloud based container image building for platforms including Linux, Windows and ARM
- can automate OS and framework patching for your docker containers
- enables automated builds triggered by source code updates, updates to a containers base image or timers
13
Q
What is ACR quick task?
A
- build and push a single container image to a container registry on demand without needing a local docker engine installation
- before you commit first line of code this feature can provide an IDE by offloading container image builds azure
- can catch potential issues prior to committing your code
14
Q
What is an ACR auto triggered task?
A
- nable one or more triggers to build an image
- trigger on source code or base image update
- trigger on a schedule
15
Q
What is a multi-step task?
A
- The single image build and push capability of ACR tasks with multi-step, multi-container-based-workflows
- defined in .yaml file
- can also define the execution of one or more containers with each step using the container as its execution env