liveBook · Manning

Ingress object

As explained in Learn Docker in a Month of Lunches, Second Edition

Ingress is the network routing layer that controls how external or internal traffic reaches an application service.

Ingress is the network routing component that controls how traffic reaches an Azure Container App. Configure a container app for internal access when only other containers in the same environment should reach it. section 14.3

For service-to-service communication, configure:

  • Internal routing, restricting the app to containers in the same Azure Container Apps environment. section 14.3
  • TCP transport and the exposed and target ports when the service uses a database protocol rather than HTTPS. section 14.3

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes
Explains internal access, TCP transport, exposed ports, target ports, and revision rollout through Azure CLI commands.
Examples
Uses a PostgreSQL database route configured internally over TCP on port 5432.
What it assumes
Assumes a deployed Azure Container Apps environment and familiarity with containerized services and Azure CLI commands.
What you can do after
Operate/configure Azure Container Apps ingress with Azure CLI for private service communication.
How it connects
Connects ingress with container environments, application configuration, secrets, database protocols, and revisions.

Also explained in

Compare how 8 books explain ingress object →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.