Administrator Fundamentals

Install and operate a self-managed Codesphere Private Cloud, following the same install guide Codesphere SREs and partners use in production.

Who this course is for

This is the operations track, not the developer track. It's built for people who will provision, install, and run Codesphere infrastructure — not for people building applications on top of it.

• You're in the right place if you're a platform/infrastructure engineer, SRE, or Kubernetes administrator who is comfortable with the Linux command line, SSH, basic Kubernetes (kubectl, namespaces, pods, services), and reading YAML. You don't need prior Codesphere experience.
• You're in the wrong place if your goal is to build and deploy an application on Codesphere day to day — that's Course A: Codesphere Developer Fundamentals, which covers Workspaces, ci.yml, and Managed Services from the application team's point of view.
• Where the line sits: Course A ends where "the platform already exists and I deploy onto it." Course B starts one layer down — "the platform doesn't exist yet and I have to stand it up and keep it healthy." If you're unsure which track fits, ask whether your day-to-day work is closer to shipping application code (Course A) or provisioning and operating the infrastructure other people ship code onto (Course B).

Format

• Pre-reading (Module 1) — self-paced, before the on-site. Platform foundations for operators: what Codesphere is, the three deployment options (Enterprise Cloud, managed private cloud, self-managed private cloud), POC vs Production topology, and the install toolchain.
• On-site course (Modules 2–3) — instructor-led, two 90-minute blocks:
    2. Install Codesphere on a Single Host — prerequisites, host prep, local bootstrap, and access from your own machine
    3. Cloud Deployment Challenge — work from a provisioned cloud environment with a jumpbox, storage nodes, and Kubernetes nodes; create your own install config and deploy

What you'll be able to do

• Explain what Codesphere is from an operator's angle, and where the platform sits on top of the infrastructure you provide.
• Plan a Codesphere install: gather inputs, choose a topology, size machines, design the network and firewall boundary.
• Work from a production-style cloud lab where the jumpbox, PostgreSQL host, Ceph nodes, and Kubernetes nodes are already provisioned.
• Build your own config.yaml and prod.vault.yaml on the jumpbox, protect the secrets correctly, and deploy Codesphere onto the provided infrastructure.
• Reason about where enforcement already exists on the platform (per-workload requests/limits, vCluster quotas) and where it's still evolving.