Cilium networking
Understand network policy and CNI enforcement.
Some app charts define Kubernetes NetworkPolicies for selected ingress and egress paths. Policies only take effect when the cluster’s CNI supports and enforces them. Kubarr does not install Cilium; Cilium is one possible policy-capable CNI, and another compatible CNI may also enforce policies. Review chart rules and verify enforcement in your cluster. Namespace separation and dashboard app permissions do not automatically block direct in-cluster service traffic.
How it works
A chart can create NetworkPolicy resources that describe which pod-to-pod and ingress or egress connections should be allowed. Kubernetes stores those rules, but the cluster CNI is responsible for enforcing them. Cilium can provide that enforcement when installed and configured as the CNI; Kubarr does not install or configure it. Check both the generated policy and CNI behavior rather than assuming the policy object alone blocks packets.
These views show or configure aspects of your Kubernetes cluster. Availability and behavior depend on your deployed components, cluster configuration and supported app charts.
Check the result: Use Kubernetes workload status and the relevant chart documentation to verify behavior. Observability views show reported state and do not themselves enforce network or storage boundaries.