Skip to content

Latest commit

 

History

History
43 lines (32 loc) · 2.5 KB

overview.md

File metadata and controls

43 lines (32 loc) · 2.5 KB

Use cases for Capsule

Using Capsule, a cluster admin can implement complex multi-tenants scenarios for both public and private deployments. Here a list of common scenarios addressed by Capsule.

Container as a Service (CaaS)

Acme Corp, our sample organization, built a Container as a Service platform (CaaS), based on Kubernetes, to serve multiple lines of business. Each line of business, has its own team of engineers that are responsible for development, deployment, and operating their digital products.

To simplify the usage of Capsule in this scenario, we'll work with the following actors:

  • Bill: he is the cluster administrator from the operations department of Acme Corp. and he is in charge of admin and maintains the CaaS platform.

  • Alice: she works as IT Project Leader at Oil & Gas Business Units, two new lines of business at Acme Corp. Alice is responsible for all the strategic IT projects and she is responsible also for a team made of different background (developers, administrators, SRE engineers, etc.) and organized in separate departments.

  • Joe: he works at Acme Corp, as a lead developer of a distributed team in Alice's organization. Joe is responsible for developing a mission-critical project in the Oil market.

  • Bob: he is the head of Engineering for the Water Business Unit, the main and historichal line of business at Acme Corp. He is responsible for development, deployment, and operating multiple digital products in production for a large set of customers.

Bill, at Acme Corp. can use Capsule to address any of the following scenarios:

NB: as we improve Capsule, more use cases about multi-tenancy and cluster governance will be covered.

What’s next

See how the cluster admin puts a new tenant onboard. Onboard a new tenant.