Cilium
Service meshcilium
eBPF CNI and sidecar-free service mesh with L7 policy, Hubble observability and optional transparent encryption.
- Provider
- default
- Kind
- Service mesh
- Category
- Operations
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| circuitBreaking | boolean | — | no | false | ▸ false |
| controlPlanes | integer | — | no | — | inherited |
| hubbleObservability | boolean | — | no | false | inherited |
| kubeProxyReplacement | boolean | — | no | false | inherited |
| managed | boolean | — | no | false | ▸ false |
| mtls | boolean | — | no | false | ▸ false |
| retries | boolean | — | no | false | ▸ false |
| sidecar | boolean | — | no | true | ▸ false |
| transparentEncryption | enum | none | ipsec | wireguard | no | none | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
No rule reads this kind yet. That is a gap, not a guarantee.
nodes:
- { id: "cilium", component: "cilium" }# yaml-language-server: $schema=../../schema/component.schema.json # Cilium: eBPF CNI and service mesh. Sidecar-free datapath (per-node Envoy only for L7), # transparent encryption (IPsec/WireGuard) is opt-in per "Encryption" in the Cilium docs. schemaVersion: "1" type: "component" id: "cilium" kind: "service-mesh" provider: "default" docs: "https://docs.cilium.io/en/stable/security/network/encryption/" defaults: managed: false sidecar: false mtls: false retries: false circuitBreaking: false properties: transparentEncryption: type: "enum" values: ["none", "ipsec", "wireguard"] default: "none" hubbleObservability: type: "boolean" default: false kubeProxyReplacement: type: "boolean" default: false