Skip to content

Cloudoor Projects

Projects is a turnkey Kubernetes adoption framework that ensures the success of daily technical operations across a multi-cloud, multi-tenant architecture.

With Projects you can:

  • Eliminate all layers of Kubernetes complexity through an intuitive surface.
  • Create and manage Kubernetes namespaces.
  • Secure projects via an included RBCA (management by roles).
  • Environment management (multi-cluster namespaces available!).
  • Optimize the management and monitoring of resources allocated by project

Projects Management (multi-cloud enabler)

As you grow, your ability to run your workloads across multi-cloud infrastructures is essential. Cloudoor Projects include native multi-tenancy framework which allows your teams to sustain their projects across their complex and heterogeneous ecosystem.

Project created on Cloudoor include:

  • Members Management with RBCA.
  • Environements Management and Monitoring.
  • Resources Management and Optimization with Quotas.
  • Tagging Strategy Management.

Teams Management

Cloudoor promotes agile team structures focused on reliable application deployment.

Via projects, Project owners build their own team composed of Developers (focused on application development), Administrators (focused on resources availability), and Viewers (focused on project monitoring) to pursue their goal of steady deployment.

Multi-cluster Namespace

You can contain multiple environments in a single project - Dev, Staging, Production, or any other type of environment you choose. For example, in each project, you can create a Dev environment on AWS-EKS, a Staging environment on OpenShift, and a Production environment on Kubernetes Vanilla located in your data center.

Resource Sharing

Projects, Project Owners and Administrators can monitor and regulate used and unused resources in their projects and between all added environments. This resource management is facilitated by the creation of Quotas.

They have the ability to set standard quotas that any project or environment can consume in terms of CPU(request & limit), Memory(request & limit), and Storage.

Info

Quotas are defined by the super-admin. This way, the organization creates a scaled resource framework, simplifies resource allocation without needing deep knowledge, and thus, eliminates potential sources of wasteage.

Name Description
CPU Request The minimum CPU capacity for all the pods in the project.
Can be defined in cores or millicores
Memory Request The minimum memory capacity you allocate to all the pods in the project.
Can be measured in M, Mi, G, Gi.
CPU Limit The maximum CPU capacity for all the pods in the project.
Can be defined in cores or millicores
Memory Limit The maximum memory capacity you can allocate to all the pods in the project.
Can be measured in M, Mi, G, Gi.
Storage The storage capacity needed by all the pods in the project.
Can be measured in M, Mi, G, Gi.

Tagging Strategy Enforcement

For deployment operations, reporting, monitoring, billing, or security, you need to effectively track your associated workloads running in your clusters.

To overcome this challenge, you can implement your Tagging strategy in two ways:

  1. You can set a tagging policy for your entire organization and make certain tags mandatory.
  2. You can give free reins to customize tags more suitable for the projects at their creation.

Further research