Skip to content

About

Public issue tracker for the F5 Playgrounds collection (Gallery, AI Playground, EOB Playground, BIG-IP Playground, and more). Source code lives in a separate private repo.

Resources

Contributing

Stars

3 stars

Watchers

0 watching

Forks

Latest commit

 

History

18 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

F5 Playgrounds — Feedback & Issue Tracker

This is the public issue tracker for F5 Playgrounds: hands-on, animated simulations of F5's portfolio that you can run in a browser. No install and no account; press Run and watch what the product does.

This repo has no source code. The playgrounds live in a separate private repository. Use it to report bugs, request features and ask questions about the live site. Feedback is read, but there is no committed response time and no commitment to implement any request. An issue is input, not a work order.


The playgrounds

Most scenarios follow the same pattern: a short premise, an animated diagram and one Run button. Most also let you compare with and without the F5 product, or flip the one setting that matters; where servers sit behind F5, each has its own on/off switch so you can take one out of service and watch traffic move. Every scenario also links to the official F5 documentation through its docs chip; where F5 hasn't published a page yet, the chip says Soon.

Recently shipped from your feedback: #1 Prefill–Decode Disaggregation · #2 Secure Agentic Delivery · #3 Direct links to any playground, module or scenario.

Playground What you can explore
Gallery The landing page. Pick any playground from here.
AI Playground How F5 delivers and secures AI. Inference (8, F5 BNK, NGINX Gateway Fabric and BIG-IP): Prompt Routing, Semantic Caching, Inference-aware Load Balancing, Prefill–Decode Disaggregation (BNK 2.4), EPP Inference Router, Token Governance, RAG Pipeline, Secure Agentic Delivery (BNK 2.4). Safety & Security (5): F5 AI Guardrails, F5 AI Red Team, F5 Workforce AI, F5 AI Powered WAF, F5 AI Gateway (in development). Data Delivery (5). AI Concepts (11 explainers, from how LLMs think to MCP). AI Threats (7 real incidents). F5 Products (the AI portfolio).
BIG-IP 45 scenarios across seven modules. LTM (8): load balancing, full proxy, DAG, SSL offload, SNAT, persistence, health monitoring, iRules. WAF (6): signatures, brute force, bot defense, behavioral L7 DoS, IP intelligence, AI Powered WAF. AFM (3). APM / Zero Trust Access (8). DNS (7). CIS for Kubernetes (7): YAML to VIP, Pool Members, Multi-Cluster, Canary Split, WAF Policy, IngressLink, TLS Modes. SSL Orchestrator (SSLO) (6, new): See Inside, Service Chains, Inbound Inspect, Smart Bypass, Tool Failure, Web Filtering. Plus a BIG-IP MCP server as a companion tool.
NGINX NGINX Plus (dynamic upstreams, cluster state sync, content caching, active health checks, WAF policy, L7 DoS), NGINX for Kubernetes (Gateway Fabric), NGINX One (fleet CVE and drift, config sync), NGINXaaS. Plus a fundamentals glossary and an MCP server tool.
F5 Distributed Cloud (XC) 19 scenarios. Multi-Cloud Networking (5), WAAP (5), Bot Defense & Fraud (6), App Delivery & Edge (3). Plus platform fundamentals and an XC MCP server tool.
F5 Insight BIG-IP fleet observability and an AI assistant: 16 scenarios across Connect, Fleet, Detect, Ask Insight, Manage and Govern.
EOB F5 eBPF Observability for 5G, built with MantisNet. Kernel-level visibility from RAN to 5G Core, through EOB and eBPF labs and a live 5G fabric.

Sharing a scenario

Every playground, module and scenario has its own link, for example https://playgrounds.amer-ent.f5demos.com/bigip/ltm/full-proxy. Copy the address bar to send someone straight to it. Please include that link in any issue too.


Filing an issue

You want to… Use
Report something broken or wrong Bug report
Suggest a scenario, feature or new playground Feature request
Ask how something works Question

A good report includes:

  • the scenario link;
  • what you expected vs what you saw;
  • your browser and OS;
  • a screenshot.

See CONTRIBUTING.md for details.

For questions about F5 products themselves, use F5 Support, not this tracker.


What happens next

  1. Acknowledged. An automated reply confirms it landed.
  2. Triaged. The issue is labelled by type, playground and priority, with a short note on how it's understood.
  3. Planned or roadmapped.
    • Work that will happen soon gets a plan.
    • Good ideas that aren't scheduled yet get the roadmap label and stay open.
  4. Shipped. When a change goes live, the issue gets a short release note with a direct link to it on the site, and is closed with the fixed label.

Some issues are closed without action, with a reason. If more detail is needed, you'll be asked in the issue.

Browse


A note on accuracy

The scenarios are conceptual demos. Product behaviour and terms follow F5's public documentation, but timings, counts and metrics are simulated for the demo, not measured product performance. If you spot a claim that doesn't match F5's docs, that's a bug we want to hear about.

Code of conduct

Be kind and assume good intent. Reports with harassment, slurs or off-topic content are closed without comment.

About

Public issue tracker for the F5 Playgrounds collection (Gallery, AI Playground, EOB Playground, BIG-IP Playground, and more). Source code lives in a separate private repo.

Resources

Contributing

Stars

3 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors