but serving Linux Containers ? (through HyperV)
Our company only want Windows OS for Prod (not linux)
https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server
So, uh, yes, it's ready for production.
This is a very strange decision. You pay a licensing cost to use Windows; the purpose of this is to be able to use Windows software and development tools. It's not going to be in any way better than using Linux directly if the goal is to host Linux containers.
I would heavily question this, if I was in an environment where my employment was safe to do so.
Otherwise - who gives a shit if it's "ready for production"? The decision has been made. Spend your employer's money and if they have made a bad choice (and they have), it's on them.
At the time, the MS tooling was garbage, and we had a lot of operational networking issues. I would pay close attention to the tooling and the ops team capabilities.
If you need to use windows in prod, use Windows. Trying to get past a policy constraint with a hack like that ultimately isn’t a good idea for a variety of reasons. It’s not saving you money if the business breaks.