"Should" is perhaps disguising the fact that these projects normally do take a lot longer than 11 weeks. I know of multiple tech companies that are years into an unfinished k8s migration. Everyone on the project will have a ton of good reasons why that project was uniquely challenged and therefore took so long.
Either the entire IT sector is inept in general or your bar is way too high. I've not seen a single K8s migration project in an actual, business running company going in under 11 weeks
> Pretty lame. If you already use docker, it shouldn't take nearly that long.
Sounds like someone has only worked with trivial, low-complexity systems and limited themselves to operating within their own capabilities.
Where's the 40 year old IBM mainframe the business depends on, and which limits customers to 8-character alphanumeric passwords? Where's the critical business system which won't run on anything higher than Java 7 and which nobody maintains? Where's the corporate policy insisting such obsolete software isn't allowed on the new system, but providing no budget or headcount to upgrade it? Where's the software that needs to connect to external services, but the team doesn't know all the hostnames or IP addresses? Where's the guy blocking DHCP and DNS because they weren't on the list of approved external services? Where's the crucial software with its license locked to a server with a certain MAC address and CPU ID?
Do you even have a sworn statement from the creators of Kubernetes that no slave labour was used? No, I thought not. Unlike you, some of us are opposed to slavery.
Google released GCP 15 years ago and they still haven't moved their internal services to use it. That proves they're web-scale and you're not.