Skip to content

Commit

Permalink
feat: bump istio 1.24.2
Browse files Browse the repository at this point in the history
Signed-off-by: Filipe Mota <[email protected]>
  • Loading branch information
fdmota committed Dec 24, 2024
1 parent e8b14ee commit cd37c6a
Show file tree
Hide file tree
Showing 101 changed files with 19,419 additions and 10,173 deletions.
5 changes: 5 additions & 0 deletions stable/istio-base/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]


## [1.24.2-1] - 2024-12-20
### Changed
- Fork of offical istio release 1.24.2. Downloaded from https://istio-release.storage.googleapis.com/charts/base-1.24.2.tgz
- Add CHANGELOG.md

## [1.19.3-1] - 2023-10-31
### Changed
- Fork of offical istio release 1.19.3. Downloaded from https://istio-release.storage.googleapis.com/charts/base-1.19.3.tgz
Expand Down
6 changes: 3 additions & 3 deletions stable/istio-base/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
apiVersion: v1
appVersion: 1.19.3
apiVersion: v2
appVersion: 1.24.2
description: Helm chart for deploying Istio cluster resources and CRDs
icon: https://istio.io/latest/favicons/android-192x192.png
keywords:
- istio
name: base
sources:
- https://github.com/istio/istio
version: 1.19.3-1
version: 1.24.2-1
14 changes: 14 additions & 0 deletions stable/istio-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

0 comments on commit cd37c6a

Please sign in to comment.