Our great sponsors
-
kubeplus
Kubernetes Operator to create multi-instance SaaS from Helm charts using Kubernetes-native APIs
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Good to know that you are developing an Operator for this custom automation to be run inside the cluster. While Operators initially were targeted towards managing some stateful application's life-cycle in Kubernetes-native manner on the cluster (such as a database), now-a-days their scope has extended to handle automation for the cluster itself (like what you are doing) and to perform reconciliation actions on things that are outside the cluster as well (think provisioning of cloud managed services). So you are on the right track here. And since you mention that you might be looking for some feedback on the Operator once it reaches some level of completeness, I thought of sharing following pointers that can help while you are developing your Operator: 1. Operator FAQ: https://github.com/cloud-ark/kubeplus/blob/master/Operator-FAQ.md 2. Operator Maturity Model: https://github.com/cloud-ark/kubeplus/blob/master/Operator-Maturity-Model.md
Related posts
- One user per pod with Kubernetes or other container orchestration tools
- Are there default limits for available memory for pods/namespaces/nodes/etc?
- Redis running on Kubernetes - Is there some reference architecture for that?
- Best Practice for cluster roles for an MSP.
- Saas application architecture examples