3 ms·

But DigitalOcean has managed K8s now: https://www.digitalocean.com/products/kubernetes/ https://www.digitalocean.com/products/kubernetes/

• atombender 7y ago
  DigitalOcean did not have Kubernetes then. Are you suggesting we should spend 6-12 man months migrating back?
  • praveenperera 7y ago
    No my mistake DOKS came out late 2018. I had been using it since May 2018 but it didn't come out of early access till December.
  • tie_ 7y ago
    How about contracting an ops-oriented person for a month that would do the migration for you? Where do those cost functions intersect?
    • atombender 7y ago
      Would never happen. Just the amount of time needed to dedicate to onboarding a temporary contractor would be really disruptive to the developers, not to mention the disruptive effect of the technical migration — databases to move over, persistent volumes to copy, DNS to repoint, lots of downtime, etc. There's a good reason companies don't switch clouds often.
      • tie_ 7y ago
        If it takes more than a month to migrate a 20-node K8s cluster, then that's a red flag. Too much tech debt or a strong vendor lock-in? Either deserves attention.
        • atombender 7y ago
          Doing the migration might take a few late evenings; deploying all our apps and Helm charts to a new cluster takes just a few commands. Learning what needs to be migrated, deciding on how the configuration should look on the destination end of it, and designing a detailed plan and checklist for the whole process is the big task. Adding the onboarding of someone who's never seen the inside of your company and you're talking about a longer, more disruptive process. Tech debt isn't a factor here.
          • praveenperera 7y ago
            > Learning what needs to be migrated, deciding on how the configuration should look on the destination end of it ... Sounds like you've identified an area of risk you should address