apiVersion: v1
name: my-bundled-apps
namespace: apps
charts:
# Map instead of list means you can not define the same chart/version
# combination more than once.
#
# Using the `@x.y.z` version notation means versions are always pinned to a
# single version, making upgrades more painful.
stable/factorio@0.1.4:
# Having the chart template values live at the top level of the chart
# configuration means no other options can be added.
factorioServer:
name: hello world
# Using non "stable" repository charts (which is always active by default)
# means you have to add the repository first, usign `helm repo add NAME URL`.
opsgoodness/prometheus-operator:
sendAnalytics: false
new
apiVersion: v1
name: my-bundled-apps
namespace: apps
charts:
# Using a list allows duplicate charts with different configuration values.
- stable/factorio:
# Semantic version constraints allows compiling the latest acceptable chart
# version.
version: ~> 0.1.0
# Using a "values" object for chart configuration values allows using more
# chart configuration keys, and makes it more clear that the configuration
# under the "values" key is the same as Helm's "values.yml"
values:
factorioServer:
name: hello world
- opsgoodness/prometheus-operator:
# When using a non-standard repository, you can provide the repository URL,
# to have kubecrt add the repository to Helm's index, before searching for
# the chart.
repo: http://charts.opsgoodness.com
values:
sendAnalytics: false
I chose not to change the apiVersion as only two internal services are using kubecrt in productionso far, and it reduces the overhead of having to maintain two different API versions. I'll update those services manually.
old
new
I chose not to change the
apiVersionas only two internal services are using kubecrt in productionso far, and it reduces the overhead of having to maintain two different API versions. I'll update those services manually.