Squid is a popular caching web proxy. There is a docker image https://hub.docker.com/r/ubuntu/squid that we can use to deploy one to a ContainerApp Environment. How? Create a VNET environment Create an external TCP app az containerapp create \ --name squid-proxy \ --resource-group $RESOURCE_GROUP \ --environment $CONTAINERAPPS_ENVIRONMENT \ --image docker.io/ubuntu/squid:5.2-22.04_beta \ --transport tcp \ --target-port 3128 \ --exposed-port 3128 \ --ingress external \ --query properties....
External and Internal ContainerApps
Every app that has an ingress, can be internal or external. Internal apps are only accessible from inside the environment. External apps are accessible from both inside, and outside the environment (defined by the VNET used or public internet if no VNET was set) External apps are accessible on {appName}.$CONTAINER_APP_ENV_DNS_SUFFIX or {appName}.internal.$CONTAINER_APP_ENV_DNS_SUFFIX Internal apps are only accessible on {appName}.internal.$CONTAINER_APP_ENV_DNS_SUFFIX All ingress-enabled apps have an .internal. endpoint by default. While only explicitly external apps will have the external endpoint....
Creating a VNET enabled ContainerApp Environment
Why? A regular ContainerApp Environment has a managed VNET, but it’s not a VNET you can access or attach other resources to. If you want to be able to attach other Azure resources (e.g: Databases, ServiceBus, Storage Accounts, etc) to a shared VNET with your apps, you’ll need to create the VNET yourself and pass it as a parameter when creating a ContainerApp Environment. Additionally some scenarios are only possible in a custom VNET environment....
Creating a ContainerApp Environment
Why? A ContainerApp Environment is a logical grouping for a set of applications (or microservices). Once you have an environment env1, you can create multiple apps on it like app1, app2, etc. When you create an app you can choose if the app is exposed externally to the environment, or just internally to other apps on the environment. External apps are accessible from the internet, unless you create them in a VNET connected environment in which case they will be available to whatever the VNET is configured for....