https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/Recent content in Architecture & Concepts on CapsuleHugo -- gohugo.ioenhttps://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/admission-policies/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/admission-policies/As Capsule we try to provide a secure multi-tenant environment out of the box, there are however some additional Admission Policies you should consider to enforce best practices in your cluster. Since Capsule only covers the core multi-tenancy features, such as Namespaces, Resource Quotas, Network Policies, and Container Registries, Classes, you should consider using an additional Admission Controller to enforce best practices on workloads and other resources. Custom Create custom Policies and reuse data provided via Tenant Status to enforce your own rules.https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/architecture/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/architecture/Key Decisions Introducing a new separation of duties can lead to a significant paradigm shift. This has technical implications and may also impact your organizational structure. Therefore, when designing a multi-tenant platform pattern, carefully consider the following aspects. As Cluster Administrator, ask yourself: 🔑 How much ownership can be delegated to Tenant Owners (Platform Users)? The answer to this question may be influenced by the following aspects: Are the Cluster Administrators willing to grant permissions to Tenant Owners?https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/known-metadata/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/known-metadata/Labels Labels commonly used in Capsule items are listed below. These labels are applied to the corresponding resources by the Capsule controller and can be used for filtering and selection purposes. capsule.clastix.io/tenant Description Target Objects Audience Established the connection between Object and Tenant. It’s value indicates the owning Tenant * Namespaces having a relationship to Tenants Controller projectcapsule.dev/tenant Description Target Objects Audience Established the connection between Object and Tenant. It’s value indicates the owning Tenant.https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/templating/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-117--docs-projectcapsule.netlify.app/docs/operating/concepts/templating/Fast Templates For simple template cases we provide a fast templating engine. With this engine, you can use Go templates syntax to reference Tenant and Namespace fields. There are no operators or anything else supported. Available fields are: {{tenant.name}}: The Name of the Tenant {{namespace}}: The Name of the namespace within the tenant (current context) Sprout Templating Our template library is mainly based on the upstream implementation from Sprout. You can find the all available functions here: