F5SPKStaticRoute¶

Overview¶

This overview discusses the F5SPKStaticRoute CR. For the full list of CRs, refer to the SPK CRs overview. The F5SPKStaticRoute Custom Resource (CR) configures the Service Proxy (SPK) Traffic Management Microkernal’s (TMM) static routing table.

This document guides you through a basic static route CR deployment.

Parameters¶

The CR spec parameters used to configure the Service Proxy TMM static routing table are:

Parameter	Description
`destination`	The IPv4 Address routing destination.
`prefixlen`	The IPv4 address subnet mask.
`gateway`	The IPv4 address of the routing gateway.
`destination_v6`	The IPv6 Address routing destination.
`prefixlen_v6`	The IPv6 address subnet mask.
`gateway_v6`	The IPv6 address of the routing gateway.
`type`	Type of route to set. The default is gateway.
`interface`	The interface that receives network traffic.

Example CR:

apiVersion: "k8s.f5net.com/v1"
kind: F5SPKStaticRoute
metadata:
  name: "staticroute-ipv4"
  namespace: spk-ingress
spec:
  destination: 10.10.1.100
  prefixLen: 32
  type: gateway
  gateway: 10.146.134.1

Requirements¶

Ensure you have:

Uploaded the Software images.
Installed the Ingress Controller Pods.
Have a Linux based workstation.

Deployment¶

Use the following steps to deploy the example F5SPKStaticRoute CR, and verify the Service Proxy TMM configuration.

Copy the Example CR into a YAML file:

apiVersion: "k8s.f5net.com/v1"
kind: F5SPKStaticRoute
metadata:
  name: "staticroute-ipv4"
  namespace: spk-ingress
spec:
  destination: 10.10.1.100
  prefixLen: 32
  type: gateway
  gateway: 10.146.134.1

Install the F5SPKStaticRoute CR:
```
oc apply -f spk-static-route.yaml
```
Verify the status of the installed CR:
```
oc get f5-spk-staticroute -n spk-ingress
```
In this example, the CR has installed successfully. An installation failure may indicate an improper configuration. For example; no route to host.
```
NAME              STATUS    MESSAGE
staticroute-ipv4  SUCCESS   CR config sent to all grpc endpoints
```
To verify the static route configuration, log in to the Service Proxy TMM container and show the routing table:

In this example, TMM is installed in the spk-ingress Project:
```
oc exec -it deploy/f5-tmm -n spk-ingress -- bash
```
```
ip route
```
In this example, the gateway IP address is a remote host on TMM’s external VLAN:
```
default via 169.254.0.254 dev tmm
10.10.1.100 via 10.146.134.1 dev external
10.20.2.0/24 dev external proto kernel scope link src 10.146.134.2
```

Feedback¶

Provide feedback to improve this document by emailing spkdocs@f5.com.