DemandFlow Support Centre

K8SNAMESPACE: K8s Namespace

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A Kubernetes namespace providing logical isolation, resource quotas, and RBAC boundaries within a cluster.

K8SNAMESPACE: K8s Namespace

A Kubernetes namespace providing logical isolation, resource quotas, and RBAC boundaries within a cluster.

Default definition. This article describes the default K8SNAMESPACE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches K8SNAMESPACE.

Entity properties

PropertyValue
Entity codeK8SNAMESPACE
Display nameK8s Namespace
PluralK8s Namespaces
Level401

Use cases

K8SNAMESPACE sits directly below K8SCLUSTER and acts as the organisational boundary for all workloads, services, configurations, storage, and policies. The cluster objectLookup field establishes the parent relationship. Purpose and environment selects allow namespaces to be tagged independently of the cluster environment, supporting multi-tenant patterns where a single cluster hosts dev, staging, and prod namespaces.

Fields

Namespace Information

FieldTypeRequiredNotes
nametextYesKubernetes namespace name
clusterreference → K8SCLUSTERYesCluster.
purposeenumValid ids: 1 (Application), 2 (Infrastructure), 3 (Development), 4 (Testing), 5 (Staging), 6 (Production), 7 (Monitoring), 8 (Security), 9 (System).
statusenumYesValid ids: 1 (Active), 2 (Terminating), 3 (Failed), 4 (Pending).
environmentenumValid ids: 1 (Production), 2 (Staging), 3 (Development), 4 (Test), 5 (QA), 6 (UAT), 7 (DR).

Resource Quotas

FieldTypeRequiredNotes
cpuRequestnumberCPU Request (cores).
cpuLimitnumberCPU Limit (cores).
memoryRequestnumberMemory Request (GB).
memoryLimitnumberMemory Limit (GB).
storageRequestnumberStorage Request (GB).
storageLimitnumberStorage Limit (GB).
podQuotanumberMaximum number of pods
serviceQuotanumberMaximum number of services

Current Usage

FieldTypeRequiredNotes
podCountnumberCurrent Pods.
serviceCountnumberCurrent Services.
cpuUsagegaugeCPU Usage %.
memoryUsagegaugeMemory Usage %.
storageUsednumberStorage Used (GB).
ingressCountnumberIngress Count.
configMapCountnumberConfigMaps.
secretCountnumberSecrets.

Labels & Annotations

FieldTypeRequiredNotes
labelstext (multi-line)Key-value pairs (JSON format)
annotationstext (multi-line)Key-value pairs (JSON format)
ownerreference → USOwner.
costCentertextCost Center.
projectCodetextProject Code.

Network & Security

FieldTypeRequiredNotes
defaultNetworkPolicyenumValid ids: 1 (Allow All), 2 (Deny All), 3 (Allow Same Namespace), 4 (Custom).
defaultServiceAccounttextDefault Service Account.
imagePullSecretstext (multi-line)Comma-separated list
podSecurityPolicytextPod Security Policy.
rbacEnabledbooleanRBAC Enabled.
isolationEnabledbooleanNetwork Isolation.

Cost Analysis

FieldTypeRequiredNotes
estimatedMonthlyCostnumberEst. Monthly Cost.
actualMonthlyCostnumberActual Monthly Cost.
cpuCostnumberCPU Cost.
memoryCostnumberMemory Cost.
storageCostnumberStorage Cost.
networkCostnumberNetwork Cost.
costTrendenumValid ids: 1 (Decreasing), 2 (Stable), 3 (Increasing).
costOptimizationScoregaugeOptimization Score.

Additional panels

  • Dashboard panel attached.

Relationships

  • Lookups: cluster points at a K8SCLUSTER record; owner points at a US record.
  • Related lists: K8SWORKLOAD, K8SSERVICE, K8SCONFIGURATION, K8SSTORAGE, K8SNETPOLICY.

Creating a K8s Namespace via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "K8SNAMESPACE",
  "level":    401,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "cluster": "",
  "status": "1",
  "purpose": "1"
}

Listing K8s Namespaces

# All records in your tenant
GET /v1/entities/K8SNAMESPACE/SUB:<your-sub-id>

See also

k8snamespacek8snamespacenamespaces

Was this article helpful?

← Back to Knowledge Base