Before you begin
Before you start the installation process, follow the steps in this section to make sure that your environment is set up to successfully install agents on the right Kubernetes clusters.
- Ensure that your version of Kubernetes is supported
Network Flow Monitor agent installation requires Kubernetes Version 1.25, or a more recent version.
- Ensure that you have installed required tools
The scripts that you use for this installation process require that you install the following tools. If you don’t have the tools installed already, see the provided links for more information.
The AWS Command Line Interface (CLI). For more information, see Installing or updating to the latest version of the AWS Command Line Interface in the AWS Command Line Interface Reference Guide.
The Helm package manager. For more information, see Installing Helm
on the Helm website. The
kubectlcommand line tool. For more information, see Install kubectlon the Kubernetes website. The
makeLinux command dependency. For more information, see the following blog post: Intro to make Linux Command: Installation and Usage. For example, do one of the following: For Debian based distributions, such as Ubuntu, use the following command:
sudo apt-get install makeFor RPM-based distributions, such as CentOS, use the following command:
sudo yum install make
- Ensure that you have valid, correctly configured KubeConfig environment variables
Network Flow Monitor agent installation uses the Helm package manager tool, which uses the kubeconfig variable,
$HELM_KUBECONTEXT, to determine the target Kubernetes clusters to work with. Also, be aware that when Helm runs installation scripts, by default, it references the standard~/.kube/configfile. You can change the configuration environment variables, to use a different config file (by updating$KUBECONFIG) or to define the target cluster you want to work with (by updating$HELM_KUBECONTEXT).- Create a Network Flow Monitor Kubernetes namespace
The Network Flow Monitor agent's Kubernetes application installs its resources into a specific namespace. The namespace must exist for the installation to succeed. To ensure that the required namespace is in place, you can do one of the following:
Create the default namespace,
amazon-network-flow-monitor, before you begin.Create a different namespace, and then define it in the
$NAMESPACEenvironment variable when you run the installation to make targets.
