2 IWF Prerequisites

This section includes information about the necessary prerequisites for IWF deployment.

Following are the prerequisites to install and configure IWF:

  • Kubernetes Cluster must be available with Kube DNS configured to talk to operator's DNS server.
  • Service FQDN of IWF must be discoverable from outside of cluster (i.e. publicly exposed if ingress messages to IWF can come from outside of K8S).
  • The user must have own repository for storing the IWF images and repository must be accessible from the Kubernetes cluster.
  • Primary/Management node must have installed with jq tool, later which will be used by config map content parsing tools

IWF Software

The IWF software includes:

  • IWF Helm chart
  • IWF docker images

The following software must be installed:

Software Version
Kubernetes v 1.15.3
HELM v 2.14.3

Additional software that needs to be deployed as per the requirement of the services:

Software Chart Version Notes
elasticsearch 1.21.1 Needed for Logging Area
elastic-curator 1.2.1 Needed for Logging Area
elastic-exporter 1.1.2 Needed for Logging Area
logs 2.0.7 Needed for Logging Area
kibana 1.5.2 Needed for Logging Area
grafana 2.2.0 Needed for Metrics Area
prometheus 8.8.0 Needed for Metrics Area
prometheus-node-exporter 1.3.0 Needed for Metrics Area
metallb 0.8.4 Needed for External IP
metrics-server 2.4.0 Needed for Metric Server
tracer 0.8.3 Needed for Tracing Area

Note:

If any of the software specified in the above table is not installed in CNE, install the software. If OCCNE is the platform, then refer Cloud Native Environment Installation Guide.

Network access

The Kubernetes cluster hosts must have network access to:

  • Local docker image repository where the IWF images are available.
  • Local helm repository where the IWF helm charts are available.

Note:

All the kubectl and helm related commands that are used in this document must be executed on a system depending on the infrastructure of the deployment. It could be a client machine, VM, server, local desktop and so on.

Client machine requirement

There are some requirements for the client machine where the deployment commands need to be executed:
  • It must have network access to the helm repository and docker image repository.
  • Helm repository must be configured on the client.
  • It should have network access to the Kubernetes cluster.
  • It should have necessary environment settings to run the kubectl commands. The environment should have privileges to create namespace in the Kubernetes cluster.
  • It should have helm client installed. The environment should be configured so that the helm install command deploys the software in the Kubernetes cluster.
  • Master/Management node must have the jq tool installed to be used by configuration map content parsing tools.
  • Operator must create MySQL NDB database cluster to store the configuration and run time data.