Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Robot Upgrade: base chart upgrade from 1.17.1 to 1.24.0 #2689

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions charts/base/base/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
apiVersion: v1
appVersion: 1.17.1
apiVersion: v2
appVersion: 1.24.0
description: Helm chart for deploying Istio cluster resources and CRDs
icon: https://istio.io/latest/favicons/android-192x192.png
keywords:
- istio
name: base
sources:
- http://github.com/istio/istio
version: 1.17.1
- https://github.com/istio/istio
version: 1.24.0
dependencies:
- name: base
version: "1.17.1"
version: "1.24.0"
repository: "https://istio-release.storage.googleapis.com/charts"
14 changes: 14 additions & 0 deletions charts/base/base/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,17 @@ To install the chart with the release name `istio-base`:
kubectl create namespace istio-system
helm install istio-base istio/base -n istio-system
```

### 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`.
8 changes: 4 additions & 4 deletions charts/base/base/charts/base/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
apiVersion: v1
appVersion: 1.17.1
apiVersion: v2
appVersion: 1.24.0
description: Helm chart for deploying Istio cluster resources and CRDs
icon: https://istio.io/latest/favicons/android-192x192.png
keywords:
- istio
name: base
sources:
- http://github.com/istio/istio
version: 1.17.1
- https://github.com/istio/istio
version: 1.24.0
14 changes: 14 additions & 0 deletions charts/base/base/charts/base/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,17 @@ To install the chart with the release name `istio-base`:
kubectl create namespace istio-system
helm install istio-base istio/base -n istio-system
```

### 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`.
Loading