Skip to content
WECORE Cloud logo
Plan a deployment

Kubernetes became the standard container orchestrator because teams can define the desired application state once and run containers consistently across infrastructure. Operating the control plane is a different job from running applications on it: etcd, the API server, the scheduler, access, templates, and version changes all need an operating model.

WECORE Cloud delivers Kubernetes as a service (KaaS) on OpenStack infrastructure your organization or service provider controls. WECORE deploys and operates the service. After the infrastructure team approves templates and access, authorized users can create a cluster from the catalog, define its single worker group, and obtain a fresh cluster-specific kubeconfig.

What the service removes and what it keeps governed

The service separates control-plane operations from application-team work while keeping infrastructure policy visible:

  • Managed control-plane operations : WECORE operates etcd, the API server, and the scheduler. Compatible version changes follow approved templates when that option is enabled for the deployment.
  • An approved template catalog : your infrastructure team decides which active templates authorized users can see, including the Kubernetes version and permitted cluster shape.
  • Preflight before resources are created : the server checks access, template eligibility, request values, and project quota before it creates credentials or cloud resources. Blocking issues and warnings are reported separately.
  • A fresh kubeconfig on demand : each download generates a new cluster-specific client credential in memory. The panel streams the kubeconfig without storing its private key.
  • One worker group with a clear boundary : every cluster has exactly one worker group. Authorized users can change its worker count within the policy set for the deployment.

From an approved template to a governed cluster

After the service is deployed and access is granted, an authorized user follows one guided workflow:

  1. Access and catalog: The infrastructure team grants access and publishes approved templates for the intended users or customers.
  2. Cluster definition: The user names the cluster and selects an approved template. The template defines the allowed Kubernetes version and control-plane shape.
  3. Worker capacity: The user chooses the size and count for the cluster's single worker group.
  4. Preflight: The service validates access, template rules, request values, and project quota before cloud resources are touched.
  5. Creation and access: The user reviews the request and creates the cluster. Status remains available on the cluster page, and each kubeconfig download produces a fresh credential.

The same server-side checks run again when the request is submitted.

Managed Kubernetes deployment

Where teams put KaaS to work

Organizations and service providers use governed Kubernetes for workloads that benefit from a consistent application platform:

  • Microservices platforms : deploy services independently while using Kubernetes primitives for rolling deployments and service discovery.
  • CI/CD delivery targets : give delivery pipelines an approved cluster target instead of asking each application team to assemble its own control plane.
  • Web and API workloads : run containerized front ends and APIs within the capacity and access policy set for the deployment.
  • Multi-tenant SaaS : separate application concerns with Kubernetes namespaces and policy on a control plane operated by WECORE.
  • Migration off bespoke infrastructure : move container workloads onto a defined service instead of maintaining a different control-plane stack for every team.
  • Batch, data, and event-driven jobs : schedule different workload types on the cluster's worker group while keeping cluster access and infrastructure policy consistent.

What you commission

An organization can commission the service for internal application teams; a service provider can commission it for authorized customers. WECORE operates the Kubernetes control plane on the OpenStack infrastructure in scope for the engagement. Your infrastructure team controls templates, access, quota, network policy, and the permitted worker configuration. Authorized users create clusters from that catalog, manage their workloads with kubectl, and download a fresh kubeconfig when needed.

Your organization or service provider defines who the service is for and which infrastructure policies apply; users receive a clear Kubernetes workflow after deployment.

To assess the service for your organization or customer offering, Request a briefing or Talk to our team. We will review the intended users, OpenStack environment, template policy, access model, and operating responsibilities with you.