History

Nikolai Rodionov 012aaadacc chore(release): Add a new release: metrics-server A new release is added to the cluster: Name: metrics-server Namespace: kube-system Version: 3.11.0 Chart: metrics-server/metrics-server		2024-09-09 09:41:17 +02:00
..
files	chore(release): Add a new release: metrics-server	2024-09-09 09:41:17 +02:00
templates	chore(release): Add a new release: metrics-server	2024-09-09 09:41:17 +02:00
Chart.yaml	chore(release): Add a new release: metrics-server	2024-09-09 09:41:17 +02:00
README.md	chore(release): Add a new release: metrics-server	2024-09-09 09:41:17 +02:00
values.yaml	chore(release): Add a new release: metrics-server	2024-09-09 09:41:17 +02:00

README.md

Istiod Helm Chart

This chart installs an Istiod deployment.

Setup Repo Info

helm repo add istio https://istio-release.storage.googleapis.com/charts
helm repo update

See helm repo for command documentation.

Installing the Chart

Before installing, ensure CRDs are installed in the cluster (from the istio/base chart).

To install the chart with the release name istiod:

kubectl create namespace istio-system
helm install istiod istio/istiod --namespace istio-system

Uninstalling the Chart

To uninstall/delete the istiod deployment:

helm delete istiod --namespace istio-system

Configuration

To view support configuration options and documentation, run:

helm show values istio/istiod

Profiles

Istio Helm charts have a concept of a profile, which is a bundled collection of value presets. These can be set with --set profile=<profile>. For example, the demo profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements.

For consistency, the same profiles are used across each chart, even if they do not impact a given chart.

Explicitly set values have highest priority, then profile settings, then chart defaults.

As an implementation detail of profiles, the default values for the chart are all nested under defaults. When configuring the chart, you should not include this. That is, --set some.field=true should be passed, not --set defaults.some.field=true.

Examples

Configuring mesh configuration settings

Any Mesh Config options can be configured like below:

meshConfig:
  accessLogFile: /dev/stdout

Revisions

Control plane revisions allow deploying multiple versions of the control plane in the same cluster. This allows safe canary upgrades

revision: my-revision-name