No questions about the architecture decisions made without knowing in details.
What about custom workloads besided databases, monitoring etc...? I guess you are providing an very straightforward way to customer to provision and run their workloads on k8s as well as easy integration with the container registry (whatever they are using).
This will become more interesting when customer requires very custom configurations to databases etc...I guess allowing them to edit the yaml of helm charts is an option but then share responsibilities etc...
Looking forward to know more about your plans with this approach
Yeah exactly that. Currently an admin Kubeconfig is exposed but proper user management will follow. From there, you are really in full control. We aim to make the repetitive stuff easy and leave the custom stuff up to you. You will have full control of the cluster.
As for custom configs, yeah we expose flags and config params to populate things that must be changed, like max_session in a db or innodb_buffer_pool, etc. But you are able to set any custom flags you want via console.
What about custom workloads besided databases, monitoring etc...? I guess you are providing an very straightforward way to customer to provision and run their workloads on k8s as well as easy integration with the container registry (whatever they are using).
This will become more interesting when customer requires very custom configurations to databases etc...I guess allowing them to edit the yaml of helm charts is an option but then share responsibilities etc...
Looking forward to know more about your plans with this approach
Cheers!