Prerequisite Knowledge

Kubernetes

Before you begin using FortiADC Kubernetes Controller, you will need to have prerequisite knowledge of the Kubernetes cluster, and Kubernetes Ingress, Service, Pod and Node. The terms and concepts discussed in this document is sourced directly from Kubernetes official documentation. For more information, please refer to the documents listed below:

• Kubernetes Concepts: https://kubernetes.io/docs/concepts/
• Kubernetes Ingress: https://kubernetes.io/docs/concepts/services-networking/ingress/
• Kubernetes Service: https://kubernetes.io/docs/concepts/services-networking/service/

Helm Charts

As Helm Charts are used in FortiADC Kubernetes Controller installation, you will also need to have understanding of how Helm Charts work. For more information, please refer to the documents listed below:

• Helm Charts values files: https://helm.sh/docs/chart_template_guide/values_files/

• Helm Charts Installation and upgrade from the Helm repository: https://helm.sh/docs/helm/helm_install/

Container Network Interface (CNI)

The resources below will help you understand where the Container Network Interface (CNI) fits into the Kubernetes architecture.

• Kubernetes network model: https://kubernetes.io/docs/concepts/cluster-administration/networking/

• Flannel: https://github.com/flannel-io/flannel

• Calico overlay networking: https://docs.tigera.io/calico/latest/networking/configuring/vxlan-ipip

  Calico supports two overlays types of encapsulation: VXLAN and IP in IP. Only VXLAN mode is supported in FortiADC Kubernetes Controller 3.1.

• Cert-Manager: https://cert-manager.io/docs/

  Starting with FortiADC Kubernetes Controller version 3.1, a webhook server is introduced. A cert-manager installation is required to generate the self-signed certificate used for the TLS connection between the Kubernetes API server and the webhook server.