ereslibre
commented
5 years ago The point behind this work is to work on operators for the new stack, but at the same time, being able to "backport" these operators to the old CaaSP; this would mean treat operators as we treat other addons (such as tiller or kubedns).
This would help us in that the operator is the one actually managing the logic of handling these resources, while salt would just submit the resources (the YAML documents themselves). This would allow us for an easier integration with the new pieces on the old world, without having to introduce many changes on the way we manage everything. It would also allow us to incrementally reduce the salt code as soon as those operators are ready and we deploy the operators on the cluster (old caasp), so they can manage the resources created by salt (that come from the UI).
The neat part IMO is that salt would be a simple mapping from database -> YAML documents [external API] submitted to the cluster, and then operators handling these documents and performing changes to the cluster as we do in Kubic today. I see this is a good balance between the old and new worlds, and how we can start "backporting" operators to the old world, increasingly removing logic from salt.
MalloZup
Depends on https://github.com/kubic-project/velum/pull/706
TODO:
Depends on https://github.com/kubic-project/velum/pull/706