Skip to content
Aa

Wingman — Prerequisites

You need F5 Distributed Cloud tenant access, a namespace with a Wingman-enabled virtual Kubernetes (vK8s) workload, an application-specific Secret Policy, xcsh, kubectl, jq, and matching Transport Layer Security (TLS) certificate/key files in private storage. Supply an explicit scoped kubeconfig and context. Use Customize examples to set your namespace, Wingman naming base, hostname, application image, and file paths; matching fields carry across the other certificate guides.

The infrastructure runbook provisions this example’s supporting policy, cluster, application, and disposable checks through Terraform plans. Complete it once if you need a working environment. Its ownership and teardown commands are operator support for this walkthrough. The steps below use that environment to demonstrate key preparation and application behavior.

Follow F5’s Wingman how-to for the platform setup and its API reference for protocol details.