showing last working render — fix the error to update
schemaHAProxy per-field validation — a subset of haproxy -c; it won't catch undefined backends, unknown keywords, or global/defaults errors.
click any line to jump to the template that produced it·Ctrl-click a keyword for its docs
Rendering…
Try this config
haptic-tryout.sh bundles the rendered haproxy.cfg with every map, error
file, and certificate it references, then runs it locally or in your cluster.
chmod +x haptic-tryout.sh
./haptic-tryout.sh [command] # no command: interactive menu
Commands
check
validate the config (haproxy -c)
run
serve it in a local Docker or Podman container
k8s
launch it as a Pod via kubectl
emit-netpol
print an allow-egress NetworkPolicy for the Pod
files
write the bundled files only
Environment variables
HAPTIC_TRYOUT_DIR
output directory (default ./haptic-tryout)
HAPTIC_TRYOUT_NAMESPACE
namespace for k8s
HAPTIC_TRYOUT_LABELS
extra Pod labels (k=v,k=v) to match a NetworkPolicy
Static snapshot: the HAPTIC controller keeps backend servers in sync as pods
change; this script does not, so a restarted target pod returns 503.
How to use the playground
The right panel is the real haproxy.cfg the HAPTIC controller would deploy —
rendered in your browser from the Templates (left) and
Resources (middle) panels. It works with Ingress (plain or with your
controller's annotations), Gateway API, or a custom CRD. Load a preset from
Start, or bring your own:
You already run HAPTIC — test a template change
Export your live config into Templates and edit it:
kubectl get htplcfg -A -o yaml
Then paste the resources it watches into Resources (commands below) and diff
the rendered output against your current haproxy.cfg — before you apply the change.
You don't run HAPTIC yet — see what it produces
In Start, pick the config that matches your setup, then paste your resources
into Resources (commands below):
Ingress
plain, or with your controller's annotations — Ingress · NGINX-Ingress, · HAProxy-Ingress, or · HAProxyTech
Gateway API
GatewayClass, Gateway, HTTPRoute, …
Custom CRD
your own resource type and templates
The resources tab then shows what each object bucketed into (and why anything
was dropped); the migration tab shows how each annotation, and each key of a pasted controller ConfigMap, carries over.
Export your resources into the Resources panel
Ingress
kubectl get ingress,service,endpointslices,secrets -A -o yaml
Gateway API
kubectl get gatewayclass,gateway,httproute,service,endpointslices,secrets -A -o yaml
Match the kinds to your watchedResources — add
grpcroutes, tcproutes, tlsroutes, or your own CRD if you
use them. Rendering does not upload your input. Shared links include the resources
you paste, and downloaded files can contain rendered secrets. Review both before sharing.
Run the playground locally
The playground renders with WebAssembly on your machine. It downloads static assets,
schemas, and examples from this site; rendering does not send your inputs to a server.
To host the whole thing yourself, build the self-contained static bundle from source
(needs Go, Helm, and yq) and serve the folder:
git clone https://gitlab.com/haproxy-haptic/haptic
cd haptic
./scripts/build-playground.sh ./playground-local dev
cd playground-local && python3 -m http.server 8080
Then open http://localhost:8080. The bundle is plain static files — HTML,
JavaScript, and WebAssembly with no third-party requests — so any static file server works.
Getting around
Click an output line
jump to the template snippet that produced it; a breadcrumb shows the full include chain
Ctrl / ⌘-click a keyword
open its docs — HAProxy directives to the config manual, Scriggo functions to the HAPTIC reference
Alt + ← / →
step back and forward through jump history (mouse thumb buttons work too)
Rendered tabs
status, applied, resources, and trace are all clickable back to their source
⤢ / Esc
maximize a panel, then Esc to restore
Compare with the solution
Left is your config, right is the solution — differences are highlighted, so you can see exactly what's missing. Close to keep working, or apply the solution to the editor.