Skip to content

Limitations and peculiarities of the WOMBAT clusters

Important: before implementation please discuss the operational aspects of the project, contact us via our ticket system with a content-related and technical description of the planned project.

Deviations from Docker Compose

If you are using a Docker Compose setup with multiple containers to develop an application locally, it is important to keep in mind that network-side access between containers within WOMBAT clusters is different:

The Docker Compose service name allows the various containers to be addressed on the network side of a Docker Compose deployment. As a result, every container can have all of the ports and is a separate host. Every service of a POD (similar to Docker Compose Setup) in WOMBAT clusters (which are based on Kubernetes) may only be reached via localhost and shares the available port set.

This means for your application:

  • Different containers must not share the same external ports.
  • If different containers communicate with each other, it must be possible to configure the addresses for network-side access via environment variables. This allows us to adapt the configuration to the specifics of Kubernetes PODs.