BIG-IP Next for Kubernetes on NVIDIA BlueField-3 DPUs can only be deployed on one DPU per chassis. Additional DPUs in the same chassis are used to accelerate GPU-to-GPU or GPU-to-storage communications.
Version notice:
F5 BIG-IP Next for Kubernetes on NVIDIA BlueField-3¶
📘Release Notes›
Learn about the latest features, fixed issues, and known issues
Installation
📘Are you curious about BIG-IP Next for Kubernetes on NVIDIA BlueField3 DPU??
Get started with BIG-IP Next for Kubernetes on NVIDIA BlueField3 DPU
📘Interested in setting up BIG-IP Next for Kubernetes on NVIDIA BlueField3 DPU for the first time??
Get started with setting up BIG-IP Next for Kubernetes on NVIDIA BlueField3 DPU
Supported Resources
📘Custom Resource Definitions (CRDs)›
Learn about Custom Resource Definitions (CRDs)
📘Troubleshooting›
Learn about Custom Resources (CRs)
Introduction
Preparing to Install
Install BIG-IP Next for Kubernetes
- F5 BIG-IP Next for Kubernetes Software Installation
- Cluster-wide RBACs for BNK
- Set-up BIG-IP Next for Kubernetes License
- Install and Configure F5 License Proxy
- Configure the Network
- Deploying Applications and Testing Traffic
- BIG-IP Next for Kubernetes CRDs
- Gateway API
- Benefits of Gateway API
- Introduction to roles in Gateway API
- Gateway API Architecture
- Prerequisites
- CNE controller
- Gateway API CRs
- Gateway API Conformance tests
- Using F5 IPAM Controller
- Firewall policy in Gateway API
- F5 iRules in Gateway API
- High-Speed Log (HSL) profiles in Gateway API
- Ingress DDoS protection in Gateway API
- Supplemental
- Feedback
How-Tos
Overviews
Troubleshooting