[Feature]: Rethink how we do ports

[svrnm]

Problem Statement

As of today the way we configure and manage ports for services is complicated and confusing:

• a service provides the HTTP entrypoint on a predefined port (8080 by default), which can be reconfigured, so accomodate docker compose (see

  app-simulator/scripts/generators/docker-compose/createComposeFile.py

  Line 19 in 3919be6

  "services": 80, # this is different from the "default default" on purpose.

  for example), as it needs port 80 to allow easy service to service communication
• k8s provides the capability to have a service port, so it can map 80 to 8080 transparently
• we allow a top level item called exposedPort (previously simply port) to make a service accessible from the outside.

This is farily complicated and also comes with a set of disadvantages:

• If we introduce additional entry points (think grpc, message queues, etc.) the "exposedPort" on top level will no longer work as it is not clear on which entry point it should be mapped
• Contributors and endusers may get confused from the amount of settings and get things configured incorrectly because they misunderstand some of the concepts.

The question is now: how can we do better?

Proposed Solution

to be done

Alternatives Considered

No response

Additional Context

No response

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing feature request