CloudRaya Documentation

KubeRaya

KubeRaya is CloudRaya’s fully managed Kubernetes platform that allows you to deploy, run, and scale containerized applications without managing the Kubernetes control plane yourself.

CloudRaya handles the complexity of the Kubernetes control plane and platform infrastructure, so you can focus on deploying applications, managing workloads, and building reliable services.

This page provides an overview of how Kubernetes works within KubeRaya, how it integrates with CloudRaya networking, and what you should understand before creating a cluster.

What KubeRaya Is (and Is Not)

What It Is

  • A managed Kubernetes control plane provided by CloudRaya
  • Integrated with CloudRaya networking and infrastructure
  • Designed for production workloads
  • Compatible with standard Kubernetes tooling (kubectl, YAML manifests)

What It Is Not

  • Not a DIY Kubernetes installation
  • Not a generic container runtime
  • Not a replacement for application configuration or CI/CD pipelines

CloudRaya manages the KubeRaya platform, while you manage your Kubernetes workloads and applications.

Getting Started

To begin using Kubernetes with KubeRaya:

  1. Create a KubeRaya cluster
  2. Access the cluster using kubeconfig
  3. Deploy your Kubernetes workloads
  4. Expose services when needed

πŸ“„ Start here:

Managing Kubernetes Clusters

Once created, KubeRaya clusters can be managed through the CloudRaya dashboard.
You can:

  • View cluster status and configuration
  • Scale worker nodes
  • Manage cluster lifecycle
  • Delete clusters when no longer needed

πŸ“„ See: Manage Clusters

Kubernetes Architecture in KubeRaya

Each Kubernetes cluster in KubeRaya is deployed within a single Cloud Zone (region).

Key Components

  • Managed Control Plane
    Operated and maintained by CloudRaya as part of the KubeRaya platform

  • Worker Nodes
    Virtual Machines that run your Kubernetes workloads

  • Platform-Managed Networking
    Kubernetes networking is handled by CloudRaya and abstracted from users

  • Kubernetes-Native Load Balancing
    Services can be exposed using standard Kubernetes Service objects

This architecture provides predictable behavior and strong isolation without requiring users to manage underlying network infrastructure.

πŸ“„ See: Architecture & Concepts

Networking Model

KubeRaya integrates with CloudRaya networking at the platform level, while preserving Kubernetes-native networking behavior.

Networking Characteristics

  • Kubernetes clusters do not run inside a user-managed VPC
  • Cluster networking is managed by the CloudRaya platform
  • Nodes use private networking internally
  • Public exposure is explicit, not automatic
  • Traffic behavior follows Kubernetes service definitions

Traffic Exposure Options

  • ClusterIP – internal-only service
  • NodePort – exposed through node-level access
  • LoadBalancer – external access via Kubernetes-native load balancing

Public access exists only when you explicitly configure it in Kubernetes.

πŸ“„ See:

Storage for Kubernetes Workloads

KubeRaya supports persistent storage by following standard Kubernetes storage abstractions, while keeping a clear separation between CloudRaya-managed infrastructure and user-managed storage integrations.

By default, KubeRaya does not provide a platform-managed Kubernetes storage service. Persistent volumes are enabled through external storage systems or application-level integrations, depending on your workload design.

Supported Storage Options

KubeRaya workloads can use:

  • Node-local storage
    Temporary or node-bound storage for stateless services and lightweight stateful workloads.

  • Object Storage integration (via S3-compatible APIs)
    Applications connect directly to external object storage for durable, shared, and cluster-independent data.

  • PersistentVolumes and PersistentVolumeClaims (via external CSI drivers)
    Kubernetes-native volumes provided by third-party or self-managed storage systems using CSI drivers.

What You Can Build

With these options, you can design:

  • Stateless services that use fast, local storage
  • Stateful applications backed by external or CSI-provided volumes
  • Durable data layers that remain available even when pods or nodes are replaced

πŸ“„ See: Storage in Kubernetes (KubeRaya)

Typical Use Cases

KubeRaya is suitable for:

  • Microservices-based applications
  • Containerized APIs
  • CI/CD-driven deployments
  • Scalable web applications
  • Internal platforms and services

If your application benefits from scaling, portability, and orchestration, Kubernetes is a strong fit.

Shared Responsibility Model

Understanding responsibility boundaries helps you operate Kubernetes on KubeRaya safely and efficiently.

CloudRaya Manages

  • Kubernetes control plane
  • Cluster API availability
  • Core control plane components
  • Platform-level networking and access integration
  • Infrastructure reliability and availability

You Manage

  • Worker node sizing and scaling
  • Kubernetes workloads (pods, services, deployments)
  • Application configuration
  • Security at the workload level
  • Resource usage inside the cluster

This separation ensures stability while preserving flexibility.

Kubernetes Security

Security in Kubernetes on KubeRaya is a shared responsibility between the platform and your workloads.

CloudRaya secures the KubeRaya infrastructure and control plane, while you control how applications are deployed, exposed, and protected inside the Kubernetes cluster.

Key security areas you should understand include:

  • How workloads communicate inside the cluster
  • How services are exposed to external traffic
  • How access is restricted at the network and application level
  • How to avoid common misconfigurations that lead to security risks

Understanding these fundamentals helps you run Kubernetes workloads that are secure by default, not secure by accident.

πŸ“„ See:

Best Practices

When using Kubernetes with KubeRaya:

  • Keep clusters scoped to a single purpose
  • Use Load Balancers instead of exposing nodes directly
  • Separate environments (development, staging, production)
  • Monitor resource usage and scaling needs
  • Treat Kubernetes as an application platform, not infrastructure

πŸ“„ See: Kubernetes Best Practices

πŸ“„ Create a KubeRaya Cluster

πŸ“„ Access a KubeRaya Cluster

πŸ“„ Manage Clusters

πŸ“„ Architecture & Concepts

πŸ“„ Networking

πŸ“„ Expose Services

πŸ“„ Network Policies (Advanced)

πŸ“„ Storage

πŸ“„ Security Basics

πŸ“„ Common Security Mistakes

πŸ“„ Best Practices

Β© 2026 CloudRaya Product Team. All rights reserved.

On this page