In containers, the network configurations are temporary.

The container configuration and the data present in the containers are not persistent between executions.

Unless and until we attach some volume to our container, the data within the containers gets lost.

This doesn’t happen to only the data; the network configuration and the IP address assigned to the container also get deleted.

A deployment is a grouping of Pods. Similar to the containers, once a Pod gets deleted, all its network configurations and IP assigned get deleted. So, the manual network configuration process becomes cumbersome.

Kubernetes provides two network availability abstractions, which makes this process easier.

The two abstractions are services and ingresses. Using this, we don’t need to worry about the underlying infrastructure or managing the IP address assignment process.