This section contains detailed documentation for all Custom Resource Definitions (CRDs).
- Tunnel - Namespace-scoped Cloudflare Tunnel
- ClusterTunnel - Cluster-wide Cloudflare Tunnel
- TunnelBinding - Bind Services to Tunnels
- VirtualNetwork - Traffic isolation network
- NetworkRoute - CIDR routing through tunnel
- PrivateService - Private IP service exposure
- WARPConnector - Site-to-site WARP connector
- AccessApplication - Zero Trust application
- AccessGroup - Reusable access policy group
- AccessIdentityProvider - Identity provider config
- AccessServiceToken - M2M authentication token
- AccessTunnel - Access-protected tunnel endpoint
- GatewayRule - DNS/HTTP/L4 policy rule
- GatewayList - List for gateway rules
- GatewayConfiguration - Global gateway settings
- DeviceSettingsPolicy - WARP client configuration
- DevicePostureRule - Device health check rule
- DNSRecord - DNS record management
- PagesProject - Cloudflare Pages project management
- PagesDeployment - Deploy versions to Pages
- PagesDomain - Custom domain for Pages
- TunnelIngressClassConfig - Ingress integration
- TunnelGatewayClassConfig - Gateway API integration
All CRDs that interact with Cloudflare API include a cloudflare spec:
spec:
cloudflare:
accountId: "your-account-id"
domain: example.com
secret: cloudflare-credentialsAll CRDs report status through standard Kubernetes conditions:
| Condition | Description |
|---|---|
Ready |
Resource is fully reconciled and operational |
Progressing |
Resource is being created or updated |
Degraded |
Resource has errors but may be partially functional |
Current API version: networking.cloudflare-operator.io/v1alpha2
Legacy version v1alpha1 is deprecated but still supported for backwards compatibility.