tl;dr: Is there a way to connect to container of a concourse task from a different container running on kubernetes?
During the integrationtesting / end-to-end-testing of our application the application send out emails. The tests should be able to receive those emails in order to validate if they are correct.
Our application consists of docker-based microservices, running in kubernetes. During the pipeline execution I would like to deploy our application via helm to kubernetes, which also sets up kubernetes services for the components. I can connect to the application from the test-task-container through such a kubernetes service. But the application must also be able to connect to the test-task-container, in order to send emails to the test.
Is this possible in Concourse? If so, can someone provide me a hint on how to make that work?
Previously we used a different tool for our pipeline in which each step of the pipeline is a docker container running in k8s (not like Concourse, which creates a runc container for each task of the pipeline in one of the concourse workers (as far as I understood the internals correct)). With this approach we were able to create a regular k8s service for the container that runs our tests (and were able to connect to that container from our application through that service).