Skip to content

CNO Onboard

CNO Onboard is built on a practical Kubernetes adoption framework that helps you onboard your organization teams and projects across all your cloud infrastructure.

You can manage your logical projects, Kubernetes environments or namespaces, and resources required like CPU, Memory, and/or Storage, from a single point of control. This enables all your teams to work together and eliminate manual tasks for an optimized time to market.

After adding your clusters to CNO Hub, you can use some best practices management capabilities.

Teams Structure

CNO promotes agile team structures focused on execution speed and innovation.

This activates groups to work together and facilitates Kubernetes adoption.

You can use and map built-in profiles within an organization regarding individual or transversal functions.

Kubernetes Multi-Cluster Projects Based On A Multi-Cloud Strategy

As your organizations use Kubernetes on a larger scale, your ability to run your workloads across multi-cloud infrastructure becomes essential.

Multitenancy allows you to onboard projects easier, reduce technical effort and usage costs, and create logical projects on different clusters.

In addition, CNO introduces a feature that enables you to create a project and then group your different namespaces to manage their configurations, monitor or security posture, and ensure compliance at any level.

For example, a Project Owner can create and manage a project specifying precisely the resources needed for:

  • Group members are working on a project like administrators, developers, or viewers.

  • Multiple namespaces across multi-cloud Kubernetes Clusters. Typically an organization may want to create a development or staging environment on EKS and a Production environment on Openshift or Rancher.

Multi-Cluster Namespaces

Quota Resource Management

A Kubernetes cluster has a limited amount of available hardware resources.

Therefore, as a best practice, you need to monitor and track the resource usage of your workloads to avoid resource exhaustion or quota constraints violations.

CNO Onboard gives you the ability to set standards quota that any project can consume in terms of CPU or Memory Request, CPU or Memory Limit, and Storage.


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

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 purposes, you need to efficiently track your related workloads running in your clusters.

For best practice, you can plan your strategy with these common considerations:

  • Tags for each type of environment, e.g., development, bench, or production;
  • Constraints tags for deployment options (Priority, Policy settings,...);
  • Criticality- whether applications are critical or not, e.g., presentation, application, or database;
  • Network tags regarding zones, locations, e.g., zone availability or regions for micro-segmentation or nano-segmentation purposes;

CNO provides a default tagging policy, but you can customize and map it to your existing tagging policy or build your own.

After the onboarding phase, all team members will have everything needed to succeed on their Day 3 Kubernetes: Business.

Project Owners and Administrators can centralize the management of Kubernetes clusters, and developers can set up their environment and deploy their applications without needing deep knowledge of every cloud provider or Kubernetes platform.

Last update: 2022-07-04