The F5 IPAM Controller runs in an orchestration environment like Kubernetes to allocate IP addresses from an IPAM system to BIG-IP Virtual Servers. The purpose is to abstract complexity related to setting up BIG-IP from a networking perspective
FIC Version : 0.1.5
CIS Version : 2.7.1
FIC Build: f5networks/f5-ipam-controller:latest
CIS Build: f5networks/k8s-bigip-ctlr:latest
BIGIP Version: Big IP x.x.x
AS3 Version: 3.x
Orchestration: K8S/OSCP
Orchestration Version:
Additional Setup details: Operator version from OLM is 0.0.1
Description
IPAM controller operator manager gets OOM Killed when reconciling F5IpamCtlr resources. The memory request/limit should raised on for the operator pod.
Steps To Reproduce
1) Install F5 IPAM controller operator
2) Create a F5IpamCtrl resource
3) The controller gets OOMKilled by Openshift dureing reconciliation.
Setup Details
FIC Version : 0.1.5 CIS Version : 2.7.1
FIC Build: f5networks/f5-ipam-controller:latest CIS Build: f5networks/k8s-bigip-ctlr:latest
BIGIP Version: Big IP x.x.x
AS3 Version: 3.x
Orchestration: K8S/OSCP
Orchestration Version:
Additional Setup details: Operator version from OLM is 0.0.1
Description
IPAM controller operator manager gets OOM Killed when reconciling F5IpamCtlr resources. The memory request/limit should raised on for the operator pod.
Steps To Reproduce
1) Install F5 IPAM controller operator 2) Create a F5IpamCtrl resource 3) The controller gets OOMKilled by Openshift dureing reconciliation.
Expected Result
Operator is not OOMKilled.