deploying-public-apps

Deploy public apps handling their own authentication by creating per-app manifests, configuring Flux kustomizations, and setting up Caddy routes without forward_auth dependencies. This automates DNS provisioning and deployment for services like Jellyfin or Minecraft.

Yes, Caddy and Flux route public Kubernetes apps managing their own login. You create per-app manifests, wire them into Flux kustomizations, and add Caddy routes without forward_auth, triggering reconciliation for end-to-end deployment.

Expose Jellyfin or Minecraft publicly by creating per-app Kubernetes manifests, updating Flux kustomizations, configuring DDNS domains, and adding Caddy routes. This handles TLS provisioning and post-deploy validation without requiring Authelia forward auth.

No, Authelia forward auth is not needed for public-facing apps that handle their own authentication. You can deploy services like Jellyfin by creating manifests, configuring Flux, and routing domains via Caddy without forward_auth dependencies.

Flux-based deployment works by wiring per-app manifests into Flux kustomizations and pushing to trigger reconciliation. This automates the end-to-end process including manifest creation, DDNS configuration, Caddy routing, and post-deploy validation for self-authenticating apps.

Deploying public apps without forward auth requires the applications to handle their own authentication securely. This approach applies to services like Jellyfin and Minecraft but is not suitable for apps lacking built-in authentication mechanisms.