Iceberg Namespace
Learn how to manage Apache Iceberg Namespaces.
IcebergNamespace resources are used to define the namespaces (databases) you want to manage in your
Iceberg catalog. A namespace groups tables and carries metadata as key/value properties.
IcebergNamespace
Specification
Here is the resource definition file for defining an IcebergNamespace.
apiVersion: "iceberg.jikkou.io/v1beta1" # The api version (required)
kind: "IcebergNamespace" # The resource kind (required)
metadata:
name: <namespace name> # Dot-separated namespace path (required)
labels: { }
annotations: { }
spec:
properties: # Namespace-level metadata (optional)
<key>: <value>
The metadata.name property is mandatory. Nested namespaces are expressed using dot notation —
for example, analytics.events creates a namespace events inside analytics.
Example
file: iceberg-namespaces.yaml
---
apiVersion: "iceberg.jikkou.io/v1beta1"
kind: "IcebergNamespace"
metadata:
name: "analytics"
spec:
properties:
owner: "data-team"
environment: "production"
---
apiVersion: "iceberg.jikkou.io/v1beta1"
kind: "IcebergNamespace"
metadata:
name: "analytics.events"
spec:
properties:
owner: "data-team"
team: "platform"
Multiple namespaces can be included in the same YAML file by separating them with
---.IcebergNamespaceList
If you need to define multiple namespaces (e.g., using a template), it may be easier to use
an IcebergNamespaceList resource.
Specification
apiVersion: "iceberg.jikkou.io/v1beta1" # The api version (required)
kind: "IcebergNamespaceList" # The resource kind (required)
metadata: { }
items: [ ] # An array of IcebergNamespace
Example
---
apiVersion: "iceberg.jikkou.io/v1beta1"
kind: "IcebergNamespaceList"
items:
- metadata:
name: "analytics"
spec:
properties:
owner: "data-team"
- metadata:
name: "analytics.events"
spec:
properties:
owner: "platform-team"
Last modified March 27, 2026: docs(iceberg): add documentation for Apache Iceberg provider (6a074f0c)