Install - Server on Kubernetes Operator Offline


Installation Wizard

To help with the installation process, vFunction offers an Installation Wizard. This Wizard provides additional information about the Prerequisites as well as the Required and Optional Settings for installing the vFunction Server and Agents. This Wizard also walks you through each step in the Installation process.

For organizations looking to start a trial with vFunction, a simplified Installation Wizard will get you started quickly without reviewing the additional Optional Settings.

Please contact support@vfunction.com or your vFunction Contact(s) for the password to start using this Wizard.


Installation Steps

Take the following steps to install the vFunction Server in a Kubernetes Cluster with no access to Docker Hub:

  1. Ensure Prerequisites are met
  2. Download the vFunction Kubernetes Operator Offline Installation TGZ
  3. SCP the Kubernetes Operator Offline Installation TGZ package to the Linux VM with kubectl access to the Kubernetes Cluster
  4. Unpack the Installation Package
### Replace VERSION with the actual value

tar -xvzf vfunction-server-offline-installation-kubernetes.vVERSION.tgz
  1. Open the installation.yaml by running the following command:
vi vfunction-server-for-kubernetes/config/installation.yaml
  1. Set the required and optional Configurable Settings
  2. Run the installation script:
### Replace NAMESPACE with the actual Namespace to be used, such as "vfunction"

bash vfunction-server-for-kubernetes/install.sh -n NAMESPACE
  1. Verify the installation was successful by running the following command.
### Replace NAMESPACE with the actual Namespace that was used, such as "vfunction"
### Verify that the "state" property shows the value "Working"
### Verify that the "installed" property shows the value "Yes"

kubectl get vfunctionserver vfunction-server -n NAMESPACE -o yaml | grep status: -A 100
  1. If, in Step #8, the “state” property shows the value “Failed”, this indicates that the Operand was not installed correctly. Check the Events and Logs for all of the Pod, the Operator and Server Containers, for any issues