Documentation
/ Reference
/ Namespaces Namespace Holds Pod Security Same-namespace traffic applicationPrometheus, Alertmanager, Grafana, Loki, Tempo, OpenCost, kube-state-metrics, blackbox exporter restricted Per component only node-agentsAlloy, node-exporter privileged None cluster-1Primary PostgreSQL cluster and its pooler restricted Allowed cluster-2Live replica cluster and its pooler restricted Allowed cluster-3Delayed replica cluster and its pooler restricted Allowed cnpg-systemCloudNativePG operator set by the upstream bundle Allowed garageGarage and its init job restricted Per component only longhorn-systemLonghorn privileged Allowed kyvernoKyverno controllers set by the upstream bundle Allowed prometheus-operatorprometheus-operator restricted Allowed falcoFalco privileged Allowed reloaderReloader restricted None natsNATS JetStream, when enabled restricted Allowed redisRedis and Sentinel, when enabled restricted Allowed kafkaStrimzi and Kafka, when enabled restricted Allowed kube-systemRKE2 components, Cilium, CoreDNS set by RKE2 Allowed
Default service accounts in every namespace have automountServiceAccountToken: false. Tenant applications get their own restricted namespaces and never run in application.
Priority classes Class Value Allowed in bedrock-storage90000000 garagebedrock-data80000000 cluster-1, cluster-2, cluster-3, falcobedrock-workload50000000 any bedrock-default10000000 any, the global default system-cluster-critical, system-node-criticalKubernetes defaults kube-system, kyverno