|
2 | 2 | head: |
3 | 3 | - - meta |
4 | 4 | - name: keywords |
5 | | - content: SEO plugin |
| 5 | + content: template operator, kubernetes, multi-tenancy, templates |
6 | 6 | --- |
7 | 7 |
|
8 | 8 | # Welcome to the Docs |
9 | 9 |
|
10 | | -[//]: # ( introduction.md, features.md) |
| 10 | +Managing Kubernetes clusters can be complex, requiring careful orchestration of resources, security, and automation. While Kubernetes provides foundational building blocks, achieving secure, scalable, and efficient multi-tenancy often demands advanced expertise and custom solutions. |
11 | 11 |
|
12 | | -Sharing Kubernetes clusters can significantly reduce costs and streamline administration. It enables efficient resource utilization, reduces configuration overhead, and simplifies the sharing of internal cluster resources among tenants. However, achieving secure and functional multi-tenancy presents challenges such as ensuring security, maintaining fairness, and mitigating the impact of noisy neighbors. |
| 12 | +**Template Operator** is designed to address these challenges by extending Kubernetes with powerful templating and automation capabilities. It enables administrators to define reusable templates for namespaces and resources, automate their distribution, and streamline the provisioning of tenant environments. With Template Operator, you can: |
13 | 13 |
|
14 | | -Kubernetes is inherently designed as a single-tenant platform. Managed Kubernetes services like AKS, EKS, GKE, and OpenShift have improved security through "secure by default" concepts, but designing and orchestrating all the moving parts required for a secure multi-tenant platform remains a complex task. This complexity makes it challenging for cluster administrators to host multiple tenants effectively within a single cluster. |
| 14 | +- **Create and manage reusable templates** for Kubernetes manifests, Helm charts, and more. |
| 15 | +- **Parameterize templates** for flexible, tenant-specific deployments. |
| 16 | +- **Automate resource distribution** across namespaces using Template Instances and Cluster Template Instances. |
| 17 | +- **Synchronize resources** such as secrets and ConfigMaps between namespaces. |
| 18 | +- **Adopt GitOps workflows** with native Kubernetes custom resources. |
| 19 | +- **Achieve multi-tenancy** without additional management layers. |
15 | 20 |
|
16 | | -Clusters can be shared in various ways: |
17 | | - |
18 | | -* Different applications might run in the same cluster. |
19 | | -* Multiple instances of the same application could operate within a single cluster, one for each end user. |
20 | | - |
21 | | -These scenarios are collectively referred to as multi-tenancy. While Kubernetes and many managed applications provide foundational resources to achieve multi-tenancy, leveraging these primitives requires professional expertise and deep knowledge of the platform. |
22 | | - |
23 | | -The Template Operator builds on Kubernetes' capabilities, simplifying the orchestration of secure and efficient multi-tenancy. By addressing the unique needs of shared clusters, Template Operator helps cluster administrators overcome the inherent complexities of multi-tenancy, enabling them to harness its full potential. |
| 21 | +Template Operator simplifies cluster administration, enhances security, and enables efficient resource utilization, making multi-tenancy accessible and manageable for organizations of all sizes. |
24 | 22 |
|
25 | 23 | ## Installation |
26 | 24 |
|
|
0 commit comments