i think the durable state machine approach is smart...that resume from where it stopped behavior is a big deal during incident response when you really dont want to rerun an entire deployment just because one step failed. K8s as a deployment target would be huge especially for the on-prem enterprise crowd. Will definitely keep an eye on that
Interesting approach. The managed self-hosting gap is real..we have run into this exact pain point with kubernetes based deployments where customers modify their cluster configs and things break silently. If I may ask how does Alien handle rollback if an update fails in a customer environment?is there any plan for on-prem/bare metal support beyond the big three clouds?
Great migration execution. The nginx reverse proxy method during DNS propagation is a smart way. we utilize a comparable approach when transitioning workloads across Kubernetes clusters but the traffic management occurs at the ingress controller level with weighted routing. I am wondering if you thought about containerizing any part of this stack during the transition or if the decision to use bare metal was deliberate in order to maintain a manageable migration scope???