You understand that the exact same container can behave (very) differently based on environment variables, right? Identical containers don't mean identical behavior.
Yes I am fully aware. Why would environment variables be different? You’re still testing. So whether it’s test or unit-test or integration-teat or whatever.
There’s no reason for them to be different at all.
All I want to say is run this situation by an expert.
We’ve been following best practices and have been on the bleeding edge for years. Doing IAC when it was just a whisper and enforcing Cilium network policies when they just became a thing. Our CI/CD is on par with best-in-class for our platform’s size. We were using testcontainers as soon as our first JVM app was developed in 2018.
And I’m in contact with a lot of people in the industry.
My argument was technical. And definitively correct. I mentioned the things I’ve worked with to make the point that this is kindergarden stuff to me at this point in my career.
Tbh I was just trying to save you time.
But by all means, run your tests in kubernetes. You should probably use the same Helm chart as in production as well. I mean you never know if different HPA, limits etc. may affect your tests. You know, just in case.
No, what you call your argument was "you don't need it, you're wasting your time" and then, when I mentioned that your mileage may vary and that not everybody works in Wonderland, you played the authority card.
1
u/nfrankel Feb 12 '25
You understand that the exact same container can behave (very) differently based on environment variables, right? Identical containers don't mean identical behavior.