Repository files navigation

The F5 BIG-IP Container Ingress Services forKubernetes andOpenShift makes F5BIG-IP services available to applications running in Kubernetes and OpenShift.

For instruction on how to use this component, see thedocsfor F5 BIG-IP Container Ingress Services for Kubernetes & OpenShift.

For guides on this and other solutions for Kubernetes, see theF5 Solution Guides for Kubernetes.

Support for Custom Resource DefinitionsDocumentation

We encourage you to use the cis-kubernetes channel in ourf5CloudSolutions Slack workspace for discussion and assistance on thiscontroller. This channel is typically monitored Monday-Friday 9am-5pm MST by F5employees who will offer best-effort support.

Contact F5 Technical support via your typical method for more time sensitivechanges and other issues requiring immediate support.

The official docker image isf5networks/k8s-bigip-ctlr.

Usually, the controller is deployed in Kubernetes. However, the controller can be run locally for development testing.

docker run f5networks/k8s-bigip-ctlr /app/bin/k8s-bigip-ctlr<args>

The official images are built using docker, but the adventurous can use standard go build tools.

Prerequisites:

• Docker

git clone https://github.com/F5Networks/k8s-bigip-ctlrcd  k8s-bigip-ctlr# Use docker to build the release artifacts, into a local "_docker_workspace" directory, then put into docker images# Debian imagemake prodOR# RHEL imagemake prod BASE_OS=ubi

A normal go toolchain can be used as well

Prerequisites:

• go 1.15
• $GOPATH pointing at a valid go workspace
• python
• virtualenv

mkdir -p$GOPATH/src/github.com/F5Networkscd$GOPATH/src/github.com/F5Networksgit clone https://github.com/f5networks/k8s-bigip-ctlrcd k8s-bigip-ctlr# Build all packages, and run unit testsmake alltest

To make changes to vendor dependencies, seeDevel