Open ctron opened 4 months ago
This feels like we should consider once we have a k8s stage environment available or maybe we intend to dockerize and can start immediately - I am a bit torn eg. the simplicity of the current setup is great and any finer grain will come with complexity/infra/config costs. Alternately, maybe this is work done outside of trustify project.
the simplicity of the current setup is great and any finer grain will come with complexity/infra/config costs.
+1 this will probably make things more complex for konflux related tasks...
Today we have a single server binary
trustd
. However, I think we need an approach to a finer grained set of processes.The main reason for that is that we might want to scale different functions independently. API services can be scaled independently. The importer server cannot, as that would lead to a concurrent run of the same importers as of today.
It would be ok to keep a single binary/container, but we would need to be able to select which features the command would provide. As a first step, it might be sufficient to just disable the importer server. On the other side, that would create a a special case just for that.