The highest tagged major version is
README
¶
F5 BIG-IP Container Ingress Services for Kubernetes & OpenShift
The F5 BIG-IP Container Ingress Services for Kubernetes and OpenShift makes F5 BIG-IP services available to applications running in Kubernetes and OpenShift.
Documentation
For instruction on how to use this component, see the docs for F5 BIG-IP Container Ingress Services for Kubernetes & OpenShift.
For guides on this and other solutions for Kubernetes, see the F5 Solution Guides for Kubernetes.
What's New?
Support for Custom Resource Definitions [Documentation] (https://github.com/F5Networks/k8s-bigip-ctlr/blob/2.x-master/docs/config_examples/customResource/CustomResource.md)
Getting Help
We encourage you to use the cis-kubernetes channel in our f5CloudSolutions Slack workspace for discussion and assistance on this controller. This channel is typically monitored Monday-Friday 9am-5pm MST by F5 employees who will offer best-effort support.
Contact F5 Technical support via your typical method for more time sensitive changes and other issues requiring immediate support.
Running
The official docker image is f5networks/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>
Building
The official images are built using docker, but the adventurous can use standard go build tools.
Official Build
Prerequisites:
- Docker
git clone https://github.com/F5Networks/k8s-bigip-ctlr
cd k8s-bigip-ctlr
# Use docker to build the release artifacts, into a local "_docker_workspace" directory, then put into docker images
# Debian image
make prod
OR
# RHEL7 image
make prod BASE_OS=rhel7
Alternate, unofficial build
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/F5Networks
cd $GOPATH/src/github.com/F5Networks
git clone https://github.com/f5networks/k8s-bigip-ctlr
cd k8s-bigip-ctlr
# Build all packages, and run unit tests
make all test
To make changes to vendor dependencies, see Devel
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
config
|
|
|
apis/cis/v1
Package v1 is the v1 version of the API.
|
Package v1 is the v1 version of the API. |
|
client/clientset/versioned
This package has the automatically generated clientset.
|
This package has the automatically generated clientset. |
|
client/clientset/versioned/fake
This package has the automatically generated fake clientset.
|
This package has the automatically generated fake clientset. |
|
client/clientset/versioned/scheme
This package contains the scheme of the automatically generated clientset.
|
This package contains the scheme of the automatically generated clientset. |
|
client/clientset/versioned/typed/cis/v1
This package has the automatically generated typed clients.
|
This package has the automatically generated typed clients. |
|
client/clientset/versioned/typed/cis/v1/fake
Package fake has the automatically generated clients.
|
Package fake has the automatically generated clients. |
|
pkg
|
|
| - | |
|
vlogger
Package vlogger implements an interface around basic logging features so that end-user and library writers can code to the interface without worrying about the specific type of logging package that is being used.
|
Package vlogger implements an interface around basic logging features so that end-user and library writers can code to the interface without worrying about the specific type of logging package that is being used. |