Watches for services in kubernetes and creates corresponding F5 irules via a VIP and iRules.
ALAMOAPI_SECRET- The path in vault to the secret for accessing the region api. The secret in vault must contain the keyslocation(url to region api),passwordandusername.F5_SECRET- The path in vault to the F5 secret. The secret in vault must contain the keyspassword,urlandusernamefor the F5 interface.CLUSTER- The cluster nameDEFAULT_DOMAIN- The default sub-domain for applications e.g.,myapp.domain.ioF5_INSIDE_MONITORandF5_MONITOR- The/PARTITION/monitorto use for monitoring node ports for the INSIDE (private) apps, and public appsF5_INSIDE_PARTITIONandF5_PARTITION- The inside and outside partition name (e.g.,DEV_INSIDE,DEV_OUTSIDE)F5_INSIDE_VIRTUALandF5_VIRTUAL- The inside and outside virtual IP name (without a partition). E.g. (inside-apps,outside-apps)INSIDE_DOMAIN- The default sub-domain for application inside e.g.,myapp-internal.domain.ioKUBERNETES_API_SERVER- The host name for the api server of kubernetesKUBERNETES_CLIENT_TYPE- The client type of kubernetes, must be set to token or cert.KUBERNETES_TOKEN_SECRET- The path in vault to the secret to access kubernetes. The vault secret must have a field calledtokenif the client type istoken. It must have fieldsadmin-crt,admin-keyandca-crtif the client type is set tocert.NAMESPACE_BLACKLIST- A comma delimited list of namespaces to instruct the service watcher not to automatically create irules for.PROFILE- If set totruethe environment variableSTACKIMPACTmust also be set to the API key for stack impact for profiling.REGIONAPI_LOCATION- The http path to the region api to use, this overrides the location set inALAMOAPI_SECRETUNIPOOL: The name of the unipool to use. This pool must contain all of the kubernetes worker nodes. The port is automatically reset in the iRule.