Create, read, update and delete load-balancer virtual servers, pools and pool members.
Manages load-balancer virtual server (VIP) and pool/pool-member objects on whichever load-balancing platform the caller is targeting, following that platform's own documented procedure exactly.
certificate-management for
that. A VIP may reference a certificate by identifier, but provisioning that certificate is out of
scope here.There is no wire-level standard grounding this capability (unlike, say, DNS) — the claims below are
verified against the four platforms currently listed in references/INDEX.md (F5 BIG-IP LTM, Citrix
ADC, HAProxy, Cloudflare Load Balancing), with the exceptions noted. Treat them as the current common
ground, not a guarantee that every future vendor added here will match:
ltm virtual's
destination; Citrix lbvserver's ipv46+port; HAProxy's frontend/bind) and the member side
is a distinct object (F5 ltm pool; Citrix service; HAProxy backend/server). Cloudflare is
the exception to the address+port part: its load balancer is identified by a DNS hostname with no
listener address, and its pools are separate objects it references.pool field, HAProxy's default_backend, Citrix's explicit
lbvserver_service_binding, and Cloudflare's list of referenced pools are all references or
bindings, never a single combined create.service.ip,
HAProxy server line, Cloudflare an origin entry identified by its name within the pool) — see each
platform's own procedure.md.session vs. state; Citrix's graceful vs.
non-graceful disable; HAProxy's maintenance/drain/health-down; Cloudflare's per-origin enabled flag
versus removing the origin). Do not normalize these into one generic "disabled" status — report the
specific mechanism actually used.See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely.
platform argument. Check
references/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet.references/<platform>/procedure.md and follow it exactly — it contains that platform's
full operational procedure, error handling, patterns, known limitations, tools, and verification
checklist.references/INDEX.md
for exact scope per vendor and known gaps. A platform not listed there needs a new reference
file before this skill can be used for it.certificate-management for that.SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error
code, a corrected field, a changed call mechanism detail — belong in that platform's own
references/<platform>/procedure.md, never here.
Each platform assumes its own authenticated client — see references/INDEX.md for which, and that
platform's procedure.md for the specific operations.
references/INDEX.md before proceedingprocedure.md was followed, including its own confirmation gates on
destructive changes (VIP deletion, pool member removal from a live pool)