F5 upgraded to Gold Membership in the Cloud Native Computing Foundation (CNCF) on March 26, 2026, during KubeCon + CloudNativeCon Europe in Amsterdam. If you've spent years configuring BIG-IP virtual servers, iRules, and health monitors, this move directly affects your career trajectory — F5 is betting its future on Kubernetes-native networking, and your existing skills transfer more than you'd expect.
TL;DR: F5's CNCF Gold Membership accelerates the convergence of traditional application delivery controllers with Kubernetes-native networking. Gateway API, OpenTelemetry, and service mesh skills are now essential for anyone working in infrastructure.
Why This Matters: The Numbers
According to the CNCF 2025 Annual Cloud Native Survey:
- 98% of organizations have adopted cloud native technologies
- 82% run Kubernetes in production (up from 66% in 2023)
- NGINX powers roughly 34% of all web servers globally
When the company behind your BIG-IP fleet and the world's most-deployed reverse proxy doubles down on Kubernetes, the signal is clear.
"Expanding to Gold Membership in the CNCF reflects our dedication to fostering innovation and collaboration in the cloud native ecosystem," said Kunal Anand, Chief Product Officer at F5.
The ingress-nginx Retirement Changes Everything
In November 2025, the Kubernetes project announced the retirement of the community-maintained ingress-nginx controller, citing maintenance challenges and security concerns. This creates a clear opening for F5's commercial NGINX Ingress Controller.
Here's how they compare:
| Feature | Community ingress-nginx (Retired) | F5 NGINX Ingress Controller |
|---|---|---|
| Configuration | Annotations (nginx.ingress.kubernetes.io/) |
CRDs (VirtualServer, Policy) |
| Protocol Support | HTTP/HTTPS primarily | HTTP, gRPC, TCP, UDP |
| WAF Integration | Limited | NGINX App Protect built-in |
| Gateway API | Partial support | Full Gateway API conformance |
| Commercial Support | Community only | F5 enterprise support |
If your organization runs ingress-nginx today, migration planning is now a near-term operational requirement.
BIG-IP Next for Kubernetes: Your ADC Skills in Container Form
BIG-IP Next for Kubernetes extends F5's traditional ADC capabilities into container environments — a single control point for ingress, egress, security, and visibility. The key difference from traditional BIG-IP is the deployment context: these functions now run as Kubernetes-native workloads, managed through Kubernetes APIs rather than TMSH or the BIG-IP GUI.
Your understanding of virtual servers, pools, iRules, and health monitors translates directly. The orchestration layer changes from CLI/GUI to Kubernetes manifests and Helm charts.
Gateway API: The Networking Abstraction You'll Actually Like
The Kubernetes Gateway API replaces the legacy Ingress resource with a role-based, protocol-flexible model. F5 is a key contributor, and their Gold Membership deepens that influence.
| Concept | Legacy Ingress | Gateway API |
|---|---|---|
| Role Separation | Single resource, single owner | GatewayClass → Gateway → Route (multi-role) |
| Protocol Support | HTTP/HTTPS only | HTTP, TCP, UDP, gRPC, TLS passthrough |
| Cross-Namespace | Not supported | Built-in ReferenceGrant mechanism |
| Extensibility | Annotations (vendor-specific) | Policy attachment model (standardized) |
| Status Reporting | Minimal | Rich status conditions per resource |
The role separation mirrors how networking teams already work:
- GatewayClass = infrastructure provider (analogous to provisioning a BIG-IP)
- Gateway = cluster operator (analogous to creating a VIP)
- HTTPRoute/TCPRoute/GRPCRoute = application developer (analogous to pool members and virtual servers)
If you've ever configured virtual servers, VIPs, and routing policies on traditional load balancers, Gateway API provides a familiar mental model wrapped in Kubernetes-native semantics.
AI Inference: Why This Is a Networking Problem
"Inference relies on scalable infrastructure, which is a fundamentally cloud native challenge enabled by CNCF technologies," said Jonathan Bryce, Executive Director of CNCF.
AI inference endpoints require:
- Low-latency load balancing — distributing requests across GPU-backed pods with health-aware routing
- Protocol flexibility — gRPC for model serving (TensorFlow Serving, Triton), HTTP/2 for API gateways
- Observability — OpenTelemetry traces and metrics across the inference pipeline
- Security — mTLS between services, WAF at ingress, rate limiting per client
Every item on that list maps to skills network engineers already possess. The platform changed from Cisco IOS to Kubernetes. The engineering principles didn't.
CNCF Membership Tiers: A Quick Reference
| Tier | Key Benefits | Notable Members |
|---|---|---|
| Silver | Community access, event discounts, project participation | Startups, regional SIs |
| Gold | Deeper project collaboration, enhanced visibility | F5, Viettel |
| Platinum | Governing Board seat, voting rights, strategic reviews | Google, AWS, Microsoft, Red Hat, Cisco |
Tracking which vendors hold Platinum and Gold positions reveals where the industry is investing.
What You Should Do This Week
Deploy a K8s lab with NGINX Ingress Controller — Install K3s or kind, deploy F5 NGINX IC, configure
VirtualServerCRDs. This is the hands-on equivalent of configuring virtual servers on BIG-IP.Study the Gateway API spec — Read the official docs and implement
GatewayClass,Gateway, andHTTPRouteresources.Instrument with OpenTelemetry — Deploy an OTel Collector and export traces/metrics from NGINX. This builds the observability muscle that AI inference environments demand.
Track CNCF project graduates — Monitor Sandbox → Incubating → Graduated transitions. These predict which technologies become enterprise defaults within 12-24 months.
The convergence of traditional ADC vendors with Kubernetes-native networking isn't a future trend — it's happening in production today.
FAQ
What does F5's CNCF Gold Membership mean for network engineers?
Deeper investment in Kubernetes-native tools like NGINX Ingress Controller and Gateway API. Expect tighter integration between traditional ADC capabilities and cloud native infrastructure.
Is Kubernetes knowledge required for network engineering roles?
Increasingly, yes. With 82% of production containers on Kubernetes and AI inference driving demand, understanding CNI plugins, service mesh, and Kubernetes networking is becoming essential.
What is the Kubernetes Gateway API?
The next-generation routing standard replacing legacy Ingress. Role-based configuration, cross-namespace routing, and multi-protocol flexibility. F5 is a key contributor.
Originally published at firstpasslab.com.
AI Disclosure: This article was adapted from original research with AI assistance. All technical facts, statistics, and quotes were verified against their cited sources. The adaptation for Dev.to was AI-assisted.
Top comments (0)