Skip to content

Commit bf85e1b

Browse files
puckpuckJaredTan95
andauthored
[demo] add mountedConfigMaps support (#1007)
* add mountedConfigMaps support Signed-off-by: Pierre Tessier <[email protected]> * add mountedConfigMaps support Signed-off-by: Pierre Tessier <[email protected]> * add mountedConfigMaps support Signed-off-by: Pierre Tessier <[email protected]> * add mountedConfigMaps support Signed-off-by: Pierre Tessier <[email protected]> --------- Signed-off-by: Pierre Tessier <[email protected]> Co-authored-by: Jared Tan <[email protected]>
1 parent fb4dbb8 commit bf85e1b

File tree

23 files changed

+596
-287
lines changed

23 files changed

+596
-287
lines changed

charts/opentelemetry-demo/Chart.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
apiVersion: v2
22
type: application
33
name: opentelemetry-demo
4-
version: 0.27.2
4+
version: 0.28.0
55
description: opentelemetry demo helm chart
66
home: https://opentelemetry.io/
77
sources:

charts/opentelemetry-demo/README.md

+42-38
Large diffs are not rendered by default.

charts/opentelemetry-demo/UPGRADING.md

+25-2
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,32 @@
11
# Upgrade guidelines
22

3+
## To 0.28
4+
5+
The `configuration` property for components has been removed in favor of the new `mountedConfigMaps` property.
6+
This new property allows you to specify the contents of the configuration using the `data` sub-property. You will also
7+
need to specify the `mountPath` to use, and give the configuration a name. The old `configuration` property used
8+
`/etc/config` and `config` as values for these respectively. The following example shows how to migrate from the old
9+
`configuration` property to the new `mountedConfigMaps` property:
10+
11+
```yaml
12+
# Old configuration property
13+
configuration:
14+
my-config.yaml: |
15+
# Contents of my-config.yaml
16+
17+
# New mountedConfigMaps property
18+
mountedConfigMaps:
19+
- name: config
20+
mountPath: /etc/config
21+
data:
22+
my-config.yaml: |
23+
# Contents of my-config.yaml
24+
```
25+
326
## To 0.24
427
5-
This release uses the [kubernetes attributes processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor)
6-
to add kubernetes metadata as resource attributes. If you override the processors array in your config, you will
28+
This release uses the [kubernetes attributes processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor)
29+
to add kubernetes metadata as resource attributes. If you override the processors array in your config, you will
730
need to add the k8s attributes processor manually to restore `service.instance.id`
831
resource attribute.
932

0 commit comments

Comments
 (0)