When Knovvu applications are deployed on a Kubernetes cluster provided by the customer, ownership of platform components may rest with either Sestek or the customer. Ownership in this context refers to the following areas:
- Deployment of the component (which party is responsible for deploying the component)
- Version update of the component (which party is responsible for updating the component)
- Technical support (which party is responsible for providing support in case of operational issues)
The table below shows the ownership per component. Ownership of some items may change depending on customer policies. The version of this table agreed upon with the customer will be recorded in the Statement of Work (SOW) document.
| Component | Ownership | Scope |
|---|---|---|
| Relational Database (MS SQL Server or PostgreSQL) | Customer | Deployment, Version Update, Technical Support |
| Redis | To be defined (Preferred Customer) | Deployment, Version Update, Technical Support |
| RabbitMQ | To be defined (Preferred Customer) | Deployment, Version Update, Technical Support |
| S3 Compatible Object Storage | Customer | Deployment, Version Update, Technical Support |
| Qdrant | Sestek | Deployment, Version Update, Technical Support |
| Elastic Stack | Sestek | Deployment, Version Update, Technical Support |
| Jenkins | Sestek | Deployment, Version Update, Technical Support |
| Vault | Sestek | Deployment, Version Update, Technical Support |
| Prometheus Stack | Customer | Deployment, Version Update, Technical Support |
Note: When Redis and RabbitMQ are provided by the customer as shared instances, resource issues in these components may impact other applications using the same instance. For this reason, provisioning these components dedicated to Sestek is preferred.