Cloud Docs - Use Case Guide to Service Proxy (SPK) for Kubernetes

Introduction

Guides for Engineers by Engineers

As F5 internal engineers, we work with the technologies and complexities created by the interconnected requirements and configurations of our customers deployments.  In doing so, we gain knowledge and insight into the eco systems that F5 products live in and learn from the people that support them.

Using GIT and Markdown

As F5 has advanced we’ve realized that the previous F5 Network Operations guides were no longer capable of keeping up with the changes to modern network infrastructure and complex configurations deployed by its users. In response, the F5 engineering teams have begun to utilize GIT and Markdown to enable the F5 community of subject matter experts in all roles to contribute and collaborate. 

Because of this shift, we able to grow the F5 Cloud Docs portal with engineer focused content like the new SPK Use Cases below.

SPK Use Cases 

The Service Proxy for Kubernetes (SPK) Use Case guide goes into detail how the OpenShift Cluster networks are connected and explains how to validate the environment to prepare for the SPK Installation while walking you through common use cases utilizing the following 5 Pods:

• Controller
• Service Proxy
• dSSM
• CWC
• Telemetry

For further information about SPK and the use cases documented check the links below: 

• Service Proxy for Kubernetes (SPK) Install
• Creating TCP Ingress for an application
• Routing diameter traffic to pods using SPK
• Enabling BGP for SPK with fault tolerance using BFD
• Enabling Egress Traffic Using SNAT
• Managing Egress Traffic Using Static Route
• SPK Egress Between Single Stack IPv4 and Single Stack IPv6 Services
• Configuring Multiple Watch Namespace
• SPK Licensing
• Macvlan Network Configuration
• Manage HTTP/2 Traffic for 5G Applications

Conclusion: 

We’re driven to keep up to date information at everyone fingertips. The new GIT and Markdown powered documentation will be one of the many tools utilized to keep you informed and operational.