-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project status #7
Comments
@masinger Any response? |
I can not speak on behalf of the original maintainer. Despite a few likes on my comments, I did not receive any substential feedback (especially regarding functionality and feature completeness). As the maintainer noted within the original issue, Kubernetes support is currently none of their priorities. The company I work for used Testcontainers in many of our customers projects and we needed this fork in order to be able to migrate into a cloud environment without support for Docker. Even though the proof of concept was working quite well (at least for our use case), the developer teams decided to replace Testcontainers altogether, as the future Kubernetes support seemed to be too uncertain. I assume that it requires quite some effort to get this PoC to a state in which it can be considered "stable" or "production ready". But as there are no foreseeable intentions to include Kubernetes support into the upstream project and me not using Testcontainers anymore, it doesn't seem to be worth the time and effort (at least at the moment). I will try to rebase and publish an updated version in the next few days and maybe I will find some spare time to improve it furthermore. Are you missing a specific feature within my fork or are you simply interested in merging it back to the upstream project? |
what did ya'll replace testcontainers with? |
+1 for @joshuasimon-taulia question Thanks in advance :) |
I'd like to know what's planned regarding turning this library into a PR in Testcontainers. I think this is the most important feature that Testcontainers can have right now.
The text was updated successfully, but these errors were encountered: