Files
wild-cloud/setup/cluster/traefik
Paul Payne f1fe4f9cc2 Settle on v1 setup method. Test run completed successfully from bootstrap to service setup.
- Refactor dnsmasq configuration and scripts for improved variable handling and clarity
- Updated dnsmasq configuration files to use direct variable references instead of data source functions for better readability.
- Modified setup scripts to ensure they are run from the correct environment and directory, checking for the WC_HOME variable.
- Changed paths in README and scripts to reflect the new directory structure.
- Enhanced error handling in setup scripts to provide clearer guidance on required configurations.
- Adjusted kernel and initramfs URLs in boot.ipxe to use the updated variable references.
2025-06-24 15:12:53 -07:00
..

Traefik

Ingress RDs can be create for any service. The routes specificed in the Ingress are added automatically to the Traefik proxy.

Traefik serves all incoming network traffic on ports 80 and 443 to their appropriate services based on the route.

Notes

These kustomize templates were created with:

helm-chart-to-kustomize traefik/traefik traefik traefik values.yaml

With values.yaml being:

ingressRoute:
  dashboard:
    enabled: true
    matchRule: Host(`dashboard.localhost`)
    entryPoints:
      - web
providers:
  kubernetesGateway:
    enabled: true
gateway:
  namespacePolicy: All