Use case of 6 different ports running on Control-Plane Pod

[Its-suLav-D]

I was wondering about the use cases of few ports running inside the pod. Some of them are self-explanatory like Validation, and Metrics but I seem to be scratching my head for the remaining.

1. default-->8080-->DEFAULT
2. control-->9999-->CONTROL
3. data-->8181-->DATA
4. validation-->8182-->VALIDATION
5. ids-->8282-->IDS
6. metrics--->9090---->METRICS

I assume data is for the datamanagement API but how about others. If I were to register my connector endpoint, would I expose the default port or the ids port ?

I appreciate your response. Thanks a lot .

[ndr-brt]

Yes, currently it's not simple to understand them.

• data stays for data-management-api so every api used to create entities as assets, contracts, etc...
• on the default there's currently exposed the health check endpoint.
• ids exposes the API needed for protocol communication

In the upstream we're going through a re-definition of the api context, so things will be easier to understand in the future.
Please check the proposal: https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/pull/2184/files#diff-67ddf95ea90aa59807801ae142bd5b1c295391944966719d6684d10775412907

[Its-suLav-D]

Thanks this definitely helps. Great job guys.