Migration to v1.0
Migration to v1.0

Migration to v1.0

Docker Cloudflare Tunnel Sync is being prepared for a stable v1.0 release.

The goal is to keep the existing behavior understandable while making the documentation, labels, and safety model clearer.

Goals

The v1.0 documentation focuses on:

  • a clearer project pitch;
  • stable label examples;
  • safer onboarding;
  • better separation between basic and advanced features;
  • clearer DNS and Access behavior;
  • a shorter README that links to the full documentation.

The basic route format remains simple:

1
2
3
4

labels:
  cloudflare.tunnel.enable: "true"
  cloudflare.tunnel.hostname: app.example.test
  cloudflare.tunnel.service: http://app:80

Multiple routes

Additional routes should use suffix-based labels:

1
2
3

labels:
  cloudflare.tunnel.hostname.admin: admin.example.test
  cloudflare.tunnel.service.admin: http://app:8080

A suffix route is only valid when both the hostname and service labels are present.

  1. Update the controller image.
  2. Run once with dry-run mode enabled.
  3. Check the planned tunnel, DNS, and Access changes.
  4. Disable dry-run mode.
  5. Enable DNS or Access synchronization only if needed.