NetBook
  • The Basics
    • About
      • 🧑‍🤝‍🧑Community
    • 🔰Getting Started
      • 🤟Introduction
    • 🛒Components
      • ⚒️WorkFlow
      • 👨‍🏫Projects
      • 🟩Dashboard
      • 🌐Workspaces
        • Overview
        • Quickstart
      • ⛏️Experiments
        • Setting Up your Code
        • Creating Training Docker Image
        • Training Data Setup
        • Start a New Training Job on NetBook UI
      • 🖥️Compute Backends
        • Add your Kubernetes Clusters
          • Create Kubernetes Cluster on E2E Nodes
          • Creating Kubernetes Cluster on Bare Metal Servers
      • 🧑‍💻Environments
        • Overview
        • Quickstart
    • 💳Accounts
      • 🌥️Bring your own Cloud
        • Azure
          • Setup in your Azure
          • Adding Credentials to Netbook Portal
        • AWS
          • Setup in your AWS account
          • Adding Credentials to NetBook Portal
    • 💵Billing
    • 🔧Settings
  • Api Docs
    • Api documentation
  • Issues and resolutions
    • Slack Support
  • Release Notes
    • Version 0
  • OpenSource
    • Docs
      • Spawner
        • reference
          • Cluster
          • Nodes
        • Setup
        • Usage examples
        • Issues and Troubleshooting
Powered by GitBook
On this page
  1. OpenSource
  2. Docs
  3. Spawner
  4. reference

Cluster

kubernetes cluster is made up of components such as control plane(master), config store i.e etcd and worker nodes.

spawner allows user to create a kubernetes cluster in the following cloud providers

  1. AWS

  2. Azure

Creating cluster

spawner create-cluster clustername -r request.json

request.json is a cluster specification file with the following fields

API fields ( *required)

field
description
Default

provider*

Backend cloud provider for infra. such aws, azure,

region*

hosted region for infra, this might change as per provider.

accountName

when using with netbook connect, you can specify the connect user whose behalf the request is made to provider. In local run this will be ignored and config provided credentials wil be used

clusterName*

Name of the cluster to be created

nodeSpec

labels

set of pair of key values. The cluster will be tagged with this ex: { created_at: sometime, by: bob}

Cluster creation takes time depending on the provider, spawner behaves differently depending on the provider

  • AWS: submit request to aws and return immediately.

  • azure: wait until cluster created and returns. TCluster and other resources (node) creation faster than other providers

PreviousreferenceNextNodes

Last updated 3 years ago

optional node specification. azure requires you to provide default system pool. Required for azure, ignored in case of aws cluster creation. Refer

nodes