☸️ Namespaces

It is advised to create the Kubernetes namespaces in advance with the following command.

Plane

plane k8s-create-namespaces

Bash

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-api
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-storage
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-cuda-operator
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-jupyter
#  labels:
#    observer.datalayer.io/prometheus: "true"
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-nginx
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-openfga
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-pulsar
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-router
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-solr
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-solr-operator
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-system
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-traefik
---
apiVersion: v1
kind: Namespace
metadata:
  name: datalayer-vault
EOF

note

This step is mandatory for now as some preliminary specs need to be applied before the Helm charts.

The below picture represents the requested namespaces and their responsibilities.

Delete Namespace

In some cases, you may need to delete and ensure the namespace resource are full terminated.

If the deletion remain stuck, the following snippet will force delete the namespace datalayer-storage.

export STUCK_NAMESPACE=datalayer-storage
kubectl get namespace "${STUCK_NAMESPACE}" -o json \
  | tr -d "\n" | sed "s/\"finalizers\": \[[^]]\+\]/\"finalizers\": []/" \
  | kubectl replace --raw /api/v1/namespaces/${STUCK_NAMESPACE}/finalize -f -