Installation¶
Objective¶
To explore troubleshooting and diagnostic commands associated with the installation of Istio.
Precheck¶
The precheck command helps ascertain that Istio can be installed or upgraded on the current Kubernetes cluster:
Install Istio¶
Istio is often installed with the istioctl
CLI in sandbox environments.
helm
is typically the method preferred for QA, staging, and production environments.
Use the Istio CLI to install Istio with the default configuration profile, which deploys istiod
and the Istio ingress gateway component:
Above, we also reference an installation configuration that configures distributed tracing.
Is istio installed properly?¶
Given an environment with Istio installed, we can verify the installation with the verify-install command:
What version of Istio am I running?¶
The version command provides version information for the CLI, the control plane, and the data plane (proxies):
Question
Part of the output from istioctl version
is:
Can you explain what this means? What proxies are being referred to?
Access Logging¶
When using the default
configuration profile, Envoy sidecars and gateways are not default-configured with access logging to standard output.
We can enable Envoy Access logging using Istio's Telemetry API.
Apply the following resource to your Kubernetes cluster:
Note that we also set the tracing provider to zipkin. More on that later.