v1.2.0

1.2.0 (2026-09-02)

Features

• alignment: port cloud-compatible scenarios, agentic tooling, and manifest probing from bnkctl family (7fec861)
• test-hosts: support -y / --yes flags on clear subcommand (b8e1d7d)

Bug Fixes

• ci: format manifest, resolve gosec warnings and clean up unused func (421287b)
• phases: remove teem url overrides, resolve config paths, and improve iface discovery idempotency (7abc055)
• scenarios/cwcadminaccess: support BNK 2.3 certificatechain fallback for mTLS verification (d8ac132)
• scenarios: enhance live verification for routes, corefiles, and cwc certs (f07f546)

v1.1.0

1.1.0 (2026-08-26)

Features

• agentcore-demo: a real stranger for path 3, and prove the firewall (6088c47)
• agentcore-demo: BNK governance + end-to-end token observability (7b23469)
• agentcore-demo: guided demo driver and a slide diagram (65c2300)
• agentcore-demo: one-command rebuild, and fix a stale-kubeconfig trap (235fa09)
• agentcore-demo: real authn/authz, a privileged tool, and honest telemetry (1089364)
• agentcore-demo: TLS on the MCP hop — and retract the "BNK can't do HTTPS" claim (e9d6534)
• ai-rig: enable AWS LB Controller addon for Envoy proxy shootout (PRD-11) (e38c1bd)
• benchmark: real Envoy-vs-BNK shootout via NodePort pre-seed (WS-E2) (3d5acf2)
• benchmark: SageMaker cold-redeploy cache reset behind --reset-cache (PRD-11 Task B) (6214e70)
• benchmark: scenario-sequence + cache-reset seam (PRD-11 Task A) (d50f09d)
• benchmark: set opt-in internal-NLB tags on forge target for non-BNK shootouts (PRD-11 Slice 4) (16fa278)
• bnk: resync --watch — auto-heal stale pool members on EndpointSlice change (779d75a)
• cli: add 'awsbnkctl topology' — whole-cluster data-path view (ASCII + mermaid) (76b9112)
• cli: add up --demo flag + demo: config block + DEMO_MODE state marker (#68) (3942d1f)
• cli: per-phase deployment lines in `awsbnkctl status` (8bfd8ab)
• cni: enable VPC CNI prefix delegation to keep pods on the primary ENI (f5d2bda)
• complete agentcore demo with gateway api routing (295f016)
• complete BNK infrastructure routing and test clients for A2A and MCP governance (006b650)
• demo: ingress-migration + external BIG-IP VE/CIS demo scenarios (9fb69bb)
• demo: promote http2+diameter assets into //go:embed packages (PRD-10 Embed slice) (#71) (9fb8c4f)
• demo: Slice A2 — inject awsbnkctl:demo + demo-expiry tags onto all AWS resources (#69) (987a36b)
• demo: Slice B — Phase17dDemoStage jumphost client pre-staging (#73) (bbbd601)
• demo: Slice C0 — demo {list,run,clean} command group + clean enumerator (#75) (c859267)
• demo: Slice C1 — http2 use-case (HTTP/2 h2c end-to-end through TMM) (PRD-10) (#76) (9d0fa97)
• demo: Slice C2 — diameter use-case (L4 CER→CEA via BNK TMM) (PRD-10) (#77) (9739318)
• demo: Slice D — green scenarios in the demo catalogue (PRD-10) (#78) (cc88256)
• forge: --register-with-forge flag on awsbnkctl up (P2) (6119a21)
• forge-benchmark: mooncake trace replay + registry-derived scenario help (WS-C2) (31c48e9)
• forge-benchmark: port forge native scenario engine (WS-C1) (90c3dcb)
• forge-benchmark: rich raw /aiperf push + object-graph linkage + aiperf install hardening (293ac3b)
• forge-enabled demo example + live rocket timer (#89) (857ae2f)
• forge: delete benchmark artifacts on down + opt-in forge cleanup (42e24c0)
• forge: make forge credentials + REST URL configurable (flag/env/yaml) (537879e)
• forge: multi-scenario benchmark presets + jumphost access-method registration (7bd4baa)
• forge: proxy shootout — run one scenario through each front-end, stamp proxy_deployment_id (WS-D1) (1735462)
• forge: wire awsbnkctl to bnk-forge over MCP transport (38a1081)
• gpu: Group 4 — Phase11cNvidiaDevicePlugin up/down + lifecycle wiring + render golden tests (0a07f6b)
• gpu: Group 5 — examples/ai-rig/cluster.yaml + example load tests (e8d747c)
• gpu: Groups 1-3 — intent fields + phase10 per-ng AMI/spot/taints/AZ + NVIDIA manifest/render (40474e3)
• host-device: pciBusID NADs + node-side MAC discovery of iface/PCI (7895000)
• intent: mandate Kubernetes 1.32 as the floor for real clusters (4ae79ea)
• lb-controller: AWS Load Balancer Controller addon for internal-NLB proxy reachability (PRD-11 Slice 1) (a94e463)
• network: sriov-external pattern — TMM DPDK dataplane over vfio-bound ENA (#92) (7eae12c)
• network: three selectable BNK interface patterns (A/B/C) (#91) (8d5c359)
• phase24c: H4 — heal pod-manager cold-start race vs kube-proxy (199675e)
• prd-11: AI LB + SageMaker demo slices + live-run fixes (checkpoint) (8abcc23)
• real agentcore project via CLI instead of dummy yaml (3ecf51f)
• replace dummy mcp with real fastmcp server and add agentcore agent code (e09f64d)
• sagemaker: Qwen-32B sizing knobs + GPU-fit preflight (PRD-11 Task C) (9d20ad2)
• scenarios: add AI how-tos #6/#7 as Amber (annotation-driven) (0a65581)
• scenarios: add egress-snat Amber scenario (F5SPKEgress AUTOMAP + pseudo-CNI VXLAN) (8edd8ed)
• scenarios:...

v1.0.0

awsbnkctl 1.0.0

We are excited to announce the 1.0.0 release of awsbnkctl, a complete CLI tool for managing F5 BIG-IP Next Kubernetes clusters on AWS!

This release marks the first stable, public version of the tool.

Key Highlights

• Full AWS Infrastructure Provisioning: Automates the creation of EKS clusters, VPCs, Subnets, and IAM roles tailored for BIG-IP Next.
• BIG-IP Next Deployment: Installs and wires the F5 Lifecycle Operator, CNE Controller, and BGP networking.
• Zero-Touch Configuration: Validates cluster.yaml manifests and ensures all configurations are correct before starting.
• Dry-run Capabilities: Validate topologies and simulate cluster deployments entirely offline without touching AWS APIs.
• Automated Lifecycle Management: Cleanly teardown and de-provision environments with awsbnkctl down.
• Cross-Platform: Available for macOS, Linux, and Windows for both x86_64 and arm64 architectures.

Examples Provided

This release includes fully functioning examples in the /examples directory to help you get started quickly:

• full-cluster: Provisions a dedicated AWS VPC, EKS cluster, node groups, and deploys a fully routed BIG-IP Next topology in one shot.
• external-only: Attaches BIG-IP Next nodes to an existing EKS cluster and configures external BGP routing.

Getting Started

Check out the Quickstart Guide in the repository to learn how to deploy your first cluster.