In order to connect to other services or databases, containers need to be instrumented with environmental variables and secrets at run time. In this video, learn how to design Dockerfiles with environmental variables and secrets, as well as use them at container image runtime.
- Environmental variables, are key valuables … that are set for the lifecycle … of the containerized application. … They can be used in the configuration of the application, … such as setting version numbers … or package installation paths … and departmental variable values … can also be written at runtime. … You can use these as external configuration … to change your application logic. … Based on the environment it's running, … some variables have added security requirements. … They can be passwords, encryption, keys, certificates, … or other types of credentials, … which be collectively called secrets. … Secrets are stored securely … in the container hosting environment. … This means that the secret implementation … is different in kubernetes versus Dockerfile … in windows versus Linux. … You should use secrets to best sensitive … and environmental variables such as database connection, … strings to containers that's runtime. … The hosting environment takes care … of storing those variables in a secure manner. …
Learn more about the AZ-400 exam at https://docs.microsoft.com/en-us/learn/certifications/exams/az-400.
- Building and running Dockerfiles
- Mounting data volumes
- Creating an Azure Container Registry
- Running apps from ACR
- Deploying ACR apps in ACI
- Creating AKS clusters
- Deploying apps to AKS