2 ms·
I'm reading this and I don't understand how what it is proposing is different from what people are already doing? > 2. Deployment. They pass the software to an
by skissane 5y ago
I'm reading this and I don't understand how what it is proposing is different from what people are already doing?
> 2. Deployment. They pass the software to another team, who are responsible for deploying it.
Use ArgoCD to deploy to K8s, and then make the developers who write the code responsible for production deployment. To deploy to production, they just get their PR approved by the right managers, and then at the appointed time click the "merge" button and ArgoCD does the rest. And part of getting approval to deploy to production, they first have to demonstrate the PR can be successfully deployed (again by ArgoCD) to a pre-production environment (pre-prod environments are isolated from each other by having a separate K8s namespace and ArgoCD application for each; and the pre-prod environments are isolated from production by putting them in a separate K8s cluster.)
I've seen firsthand that model work. What is Cthulix adding to it?
There is a section "What about Kubernetes?" – but it doesn't clearly explain how Cthulix and K8s differ, and what problems the author sees with the K8s model, and how Cthulix will avoid them. "If you use K8s like that, it will lead to the algorithms-first mess warned about early in this paper" is a very vague statement, and even supposing it were (in some sense) true, it isn't clear why the solution to that "mess" has to be a whole new system as opposed to just a different way of using K8s, or some evolutionary changes to K8s (new operators or whatever)