• nickwitha_k (he/him)@lemmy.sdf.org
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Yes. Because I intentionally design systems to avoid vendor lock-in by, at the very least, including a plan to export data and keep IaC in a repo so that it can be used to redeploy at either another vendor or colo-based servers.

    Here’s some good tools to do so:

    • Foreman Self-managed Metal-as-a-Service/VM-as-a-Service orchestrator. It’s FOSS.
    • Terraform Formerly FOSS, now moving to BSL due to service providers taking advantage of them. IaC tooling that allows one to rapidly deploy and manage infra on multiple platforms.
    • Keycloak FOSS IAM platform that’s pretty straightforward to use.
    • Talos Many choices here but I’ve used Talos before. It’s a FOSS K8S-specific Linux distro that is designed to be platform agnostic and auto-deployed with a simple config.
    • Helm K8S deployment manager. Need a DB? You can probably find a chart.

    There’s a ton of other possibilities but FOSS and source-availabile licensed software makes it pretty straightforward (though still time-consuming as no infra is fully cloud agnostic due to non-standardization between the big three in infra primitives).

      • nickwitha_k (he/him)@lemmy.sdf.org
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        That wasn’t in the initial reqs. And, supposing the hardware was good to go, about the same as AWS.

        ETA: The time/click savings is more likely to be in maintenance because using a cloud service is just paying someone else to do that for you.