create-project

name	create-project
description	Create a new Kube-DC project with isolated VPC networking inside an existing organization. Handles network type selection (cloud vs public), organization verification, and project manifest generation.

Prerequisites

• Organization must exist and be Ready
• User must have admin access to the organization
• Check org quota for project limits before creating

Steps

1. Verify Organization Exists

kubectl get organization {org-name} -n {org-name}

The organization namespace is the same as the organization name.

2. Choose Network Type

Type	When to Use
cloud (recommended)	Web apps, APIs, microservices — shared NAT gateway, more secure
public	Game servers, direct IP needs — dedicated public gateway IP

Default to cloud unless the user explicitly needs dedicated public IPs.

3. Apply Project Manifest

apiVersion: kube-dc.com/v1
kind: Project
metadata:
  name: {project-name}
  namespace: {org-name}
spec:
  cidrBlock: 10.0.0.0/16        # required — internal VPC subnet for this project
  egressNetworkType: cloud      # or: public

cidrBlock is required (CRD validation enforces it). Use 10.0.0.0/16 unless you have a specific reason to overlap with another network — each project gets its own VPC, so the same CIDR can be reused across projects.

See @project-template.yaml for the full template.

4. Wait for Ready

kubectl get project {project-name} -n {org-name} -w

The project creates namespace {org-name}-{project-name} with:

• Isolated VPC subnet (Kube-OVN)
• Default network {org-name}-{project-name}/default
• SSH keypair secrets (ssh-keypair-default, authorized-keys-default)
• Default gateway EIP

5. Verify Resources

kubectl get project {project-name} -n {org-name}
kubectl get secret ssh-keypair-default -n {org-name}-{project-name}
kubectl get eip -n {org-name}-{project-name}

Verification

After applying, run these checks to confirm the project was created successfully:

# 1. Check project phase (expect: Ready)
kubectl get project {project-name} -n {org-name} -o jsonpath='{.status.phase}'

# 2. Verify project namespace was created
kubectl get ns {org-name}-{project-name}

# 3. Verify SSH keypair exists in project namespace
kubectl get secret ssh-keypair-default -n {org-name}-{project-name}

# 4. Verify default gateway EIP was created
kubectl get eip -n {org-name}-{project-name}

Success: Phase is Ready, namespace exists, SSH keypair and EIP present. Failure: If phase is Pending or Failed, check events: kubectl describe project {project-name} -n {org-name}

Safety

• Always verify org exists before creating project
• Default to cloud network type
• Project names must be lowercase, alphanumeric with hyphens
• One project = one VPC = one subnet — this is the isolation boundary