Create FAR secret in namespaces

In order to successfully install the F5 Lifecycle Operator (FLO) and BIG-IP Next for Kubernetes, the user is required to create the FAR secret within the default, f5-utils, or any other designated namespace where flo-values.yaml or bnkgatewayclass-cr.yaml are applied. This will enable you pull the docker images required for FLO and BIG-IP Next for Kubernetes installation. In the Kubernetes environment, the default namespace serves as the default location for resources if a specific namespace is not created and specified.

Note: BNKGatewayClass CR deployment will deploy the product in default namespace, which is not a recommended way. It is expected for the customer to provide a non-default tenant namespace while installing FLO helm-chart, which will deploy FLO in the user provided tenant namespace. BNKGatewayClass CR needs to be deployed in the same tenant namespace.

Prerequisites:

Before you create FAR secret in any namespace, ensure that the following prerequisites are met:

  • Created the f5-utils and other required namespaces according to your planned configuration.

  • Created the far-secret.yaml file, see Create FAR secret.

Use the following instructions to create FAR secrets in namespaces:

  1. Create a f5-utils namespace that is used to install shared FLO components such as CWC, RabbitMQ, and DSSM. For more information see Install BIG-IP Next for Kubernetes.

    kubectl create ns f5-utils

  2. Apply the far-secret.yaml secret file on the namespaces default and f5-utils or other namespace where you plan to install FLO and BIG-IP Next for Kubernetes.

    In the below example f5-utils is the namespace.

    kubectl create -f far-secret.yaml -n f5-utils