content/en/about/faq/setup/install-method-selection.md
In addition to the simple getting started evaluation install, there are several different methods you can use to install Istio. Which one you should use depends on your production requirements. The following lists some of the pros and cons of each of the available methods:
The simplest and most qualified installation and management path with high security. This is the community recommended method for most use cases.
Pros:
IstioOperator API which provides extensive configuration/customization options.Cons:
istioctl command can set values automatically based on your running environment,
thereby producing varying installations in different Kubernetes environments.Allows easy integration with Helm-based workflows and automated resource pruning during upgrades.
Pros:
Cons:
istioctl install.Apply a generated Kubernetes manifest
This method is suitable where strict auditing or augmentation of output manifests is required, or there are third-party tooling constraints.
Pros:
helm or istioctl.kubectl.Cons:
Installation instructions for all of these methods are available on the Istio install page.