4 ms·

Pretty lame. If you already use docker, it shouldn't take nearly that long. If you don't, then kube isn't the problem for any migration similar

by stn_za 3y ago

blowski 3y ago
"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.
- stn_za 3y ago
  Yeah, when you have inept people. Hackernews however is a frounder, frontend scene first site. So I'd imagine that is what normal feels like to most of you.
  - masterinept 3y ago
    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
  - snapcaster 3y ago
    How long do the k8s migration projects take you and your team?
Draiken 3y ago
You'd be surprised. I still see a lot of companies using something like Heroku or other custom solutions.
michaelt 3y ago
> 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. /s

Pretty lame. If you already use docker, it shouldn't take nearly that long. If you don't, then kube isn't the problem for any migration similar

by stn_za 3y ago

Pretty lame. If you already use docker, it shouldn't take nearly that long. If you don't, then kube isn't the problem for any migration similar

blowski 3y ago

"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.

stn_za 3y ago
Yeah, when you have inept people. Hackernews however is a frounder, frontend scene first site. So I'd imagine that is what normal feels like to most of you.
- masterinept 3y ago
  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
- snapcaster 3y ago
  How long do the k8s migration projects take you and your team?

Draiken 3y ago

You'd be surprised. I still see a lot of companies using something like Heroku or other custom solutions.

michaelt 3y ago

> 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. /s