F5 Container Integrations v1.2

Current Page

Application Services Proxy

Cloud Foundry

Kubernetes

Mesos Marathon

OpenShift

Support

Troubleshooting

Tutorials

Cloud Docs Home > F5 Container Integrations Index

Configure the BIG-IP Controller for Marathon

When you launch the BIG-IP Controller for Marathon, you must provide the required configuration parameters shown in the table below. Define these configuration parameters in the "env" section of the Marathon Application definition file.

Required configuration parameters

Parameter Description
MARATHON_URL Marathon service URL (e.g., http://10.190.25.75:8080)
F5_CC_BIGIP_USERNAME Username for BIG-IP account with permission to manage objects in the specified partition
F5_CC_BIGIP_PASSWORD Password for BIG-IP account
F5_CC_BIGIP_HOSTNAME BIG-IP Hostname/IP address
F5_CC_PARTITIONS The BIG-IP partition BIG-IP Controller should manage
Example Application definition
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
// REMOVE ALL COMMENTS FROM THIS FILE BEFORE USING
{
  "id": "marathon-bigip-ctlr",
  "cpus": 0.5,
  "mem": 64.0,
  "instances": 1,
  "container": {
    "type": "DOCKER",
    "docker": {
      // replace the version as needed
      "image": "f5networks/marathon-bigip-ctlr:1.1.0",
      "network": "BRIDGE"
    }
  },
  "env": {
    "MARATHON_URL": "http://10.190.25.75:8080",
    "F5_CC_PARTITIONS": "mesos",
    "F5_CC_BIGIP_HOSTNAME": "10.190.25.80",
    "F5_CC_BIGIP_USERNAME": "admin",
    "F5_CC_BIGIP_PASSWORD": "admin",
    // Mesos DC/OS Enterprise Authentication
    "F5_CC_DCOS_AUTH_CREDENTIALS": "{ \"scheme\": \"RS256\", \"uid\": \"my-dcos-account\", \"login_endpoint\": \"https://10.190.25.75:8080/acs/api/v1/auth/login\", \"private_key\": \"<my-private_key-string>\" }",
    "F5_CC_MARATHON_CA_CERT": "<marathon_ca_cert>"
    // Mesos DC/OS Open oath authentication
    "F5_CC_DCOS_AUTH_TOKEN": "<authentication-token>"
  }
}

Required Application Labels

Use the F5 application labels listed in the table below when you’re managing BIG-IP Local Traffic Manager (LTM) objects directly.

Parameter Description
F5_PARTITION The BIG-IP partition in which you want to create a virtual server; cannot be “/Common”.
F5_{n}_BIND_ADDR

IP address to use for the BIG-IP LTM virtual server created for the Marathon App service [1]

Example: "F5_0_BIND_ADDR": "10.0.0.42"

F5_{n}_PORT

Service port to use on the BIG-IP LTM virtual server. Overrides the servicePort configuration parameter.

Example: "F5_0_PORT": "80"

[1]Not required when creating unattached pools.

Required iApp Application Labels

Use the F5 application labels when deploying an iApp.

Parameter Description
F5_PARTITION The BIG-IP partition in which you want to create a virtual server; cannot be “/Common”.
F5_{n}_IAPP_TEMPLATE The iApp template you want to use to create the Application Service; must already exist on the BIG-IP.
F5_{n}_IAPP_TABLE_* Template-specific [2]
F5_{n}_IAPP_POOL_MEMBER_TABLE Template-specific [2]
F5_{n}_IAPP_VARIABLE_* Template-specific [2]
F5_{n}_IAPP_OPTION_* Template-specific [2]
[2](1, 2, 3, 4) See Application Labels for iApp Mode for more information.

See Also

See the marathon-bigip-ctlr product documentation for the full list of available configuration parameters.