changed username

Signed-off-by: Christian Kotzbauer <christian.kotzbauer@gmail.com>
This commit is contained in:
Christian Kotzbauer 2020-05-15 09:31:54 +02:00
parent 3252895075
commit 063fd5333d
9 changed files with 297 additions and 297 deletions

View File

@ -1,22 +1,22 @@
# Helm Charts # Helm Charts
[![](https://github.com/code-chris/helm-charts/workflows/Release%20Charts/badge.svg?branch=master)](https://github.com/code-chris/helm-charts/actions) [![](https://github.com/ckotzbauer/helm-charts/workflows/Release%20Charts/badge.svg?branch=master)](https://github.com/ckotzbauer/helm-charts/actions)
[![Mergify Status][mergify-status]][mergify] [![Mergify Status][mergify-status]][mergify]
[mergify]: https://mergify.io [mergify]: https://mergify.io
[mergify-status]: https://img.shields.io/endpoint.svg?url=https://gh.mergify.io/badges/code-chris/helm-charts&style=flat-square [mergify-status]: https://img.shields.io/endpoint.svg?url=https://gh.mergify.io/badges/ckotzbauer/helm-charts&style=flat-square
## Usage ## Usage
Add the repo: Add the repo:
``` ```
helm repo add code-chris https://code-chris.github.io/helm-charts helm repo add ckotzbauer https://ckotzbauer.github.io/helm-charts
``` ```
## Charts ## Charts
- [cadvisor](https://github.com/code-chris/helm-charts/tree/master/charts/cadvisor) - [cadvisor](https://github.com/ckotzbauer/helm-charts/tree/master/charts/cadvisor)
- [nfs-client-provisioner](https://github.com/code-chris/helm-charts/tree/master/charts/nfs-client-provisioner) - [nfs-client-provisioner](https://github.com/ckotzbauer/helm-charts/tree/master/charts/nfs-client-provisioner)
- [prometheus-blackbox-exporter](https://github.com/code-chris/helm-charts/tree/master/charts/prometheus-blackbox-exporter) - [prometheus-blackbox-exporter](https://github.com/ckotzbauer/helm-charts/tree/master/charts/prometheus-blackbox-exporter)
- [prometheus-msteams](https://github.com/code-chris/helm-charts/tree/master/charts/prometheus-msteams) - [prometheus-msteams](https://github.com/ckotzbauer/helm-charts/tree/master/charts/prometheus-msteams)

View File

@ -1,16 +1,16 @@
apiVersion: v1 apiVersion: v1
description: A chart for a Cadvisor deployment description: A chart for a Cadvisor deployment
name: cadvisor name: cadvisor
version: 1.1.0 version: 1.1.1
appVersion: 0.36.0 appVersion: 0.36.0
home: https://github.com/google/cadvisor home: https://github.com/google/cadvisor
sources: sources:
- https://github.com/google/cadvisor - https://github.com/google/cadvisor
- https://github.com/code-chris/helm-charts - https://github.com/ckotzbauer/helm-charts
keywords: keywords:
- prometheus - prometheus
- cadvisor - cadvisor
- monitoring - monitoring
maintainers: maintainers:
- name: code-chris - name: ckotzbauer
email: christian.kotzbauer@gmail.com email: christian.kotzbauer@gmail.com

View File

@ -1,76 +1,76 @@
# Cadvisor # Cadvisor
A chart for a Cadvisor deployment A chart for a Cadvisor deployment
Learn more: [https://github.com/google/cadvisor](https://github.com/google/cadvisor) Learn more: [https://github.com/google/cadvisor](https://github.com/google/cadvisor)
## TL;DR; ## TL;DR;
```bash ```bash
$ helm install code-chris/cadvisor $ helm install ckotzbauer/cadvisor
``` ```
## Introduction ## Introduction
This chart creates a daemonset on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. This chart creates a daemonset on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
## Prerequisites ## Prerequisites
- Kubernetes 1.10+ - Kubernetes 1.10+
## Installing the Chart ## Installing the Chart
To install the chart with the release name `my-release`: To install the chart with the release name `my-release`:
```bash ```bash
$ helm install --name my-release code-chris/cadvisor $ helm install --name my-release ckotzbauer/cadvisor
``` ```
The command deploys the Cadvisor on the Kubernetes cluster using the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. The command deploys the Cadvisor on the Kubernetes cluster using the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
## Uninstalling the Chart ## Uninstalling the Chart
To uninstall/delete the `my-release` deployment: To uninstall/delete the `my-release` deployment:
```bash ```bash
$ helm delete my-release $ helm delete my-release
``` ```
The command removes all the Kubernetes components associated with the chart and deletes the release. The command removes all the Kubernetes components associated with the chart and deletes the release.
## Configuration ## Configuration
The following table lists the configurable parameters of the Prometheus MSTeams chart and their default values. The following table lists the configurable parameters of the Prometheus MSTeams chart and their default values.
| Parameter | Description | Default | | Parameter | Description | Default |
| -------------------------- | ------------------------------------------------ | --------------------- | | -------------------------- | ------------------------------------------------ | --------------------- |
| `image.repository` | container image repository | `k8s.gcr.io/cadvisor` | | `image.repository` | container image repository | `k8s.gcr.io/cadvisor` |
| `image.tag` | container image tag | `v0.36.0` | | `image.tag` | container image tag | `v0.36.0` |
| `image.pullPolicy` | container image pull policy | `IfNotPresent` | | `image.pullPolicy` | container image pull policy | `IfNotPresent` |
| `nodeSelector` | node labels for pod assignment | `{}` | | `nodeSelector` | node labels for pod assignment | `{}` |
| `tolerations` | node tolerations for pod assignment | `[]` | | `tolerations` | node tolerations for pod assignment | `[]` |
| `affinity` | node affinity for pod assignment | `{}` | | `affinity` | node affinity for pod assignment | `{}` |
| `container.port` | the container and service port to use | 8080 | | `container.port` | the container and service port to use | 8080 |
| `container.additionalArgs` | additional container arguments | see values.yaml | | `container.additionalArgs` | additional container arguments | see values.yaml |
| `container.hostPaths` | hostPaths to mount in the container | see values.yaml | | `container.hostPaths` | hostPaths to mount in the container | see values.yaml |
| `resources` | pod resource requests & limits | `{}` | | `resources` | pod resource requests & limits | `{}` |
| `serviceAccount.create` | create a own serviceAccount for the pod | `true` | | `serviceAccount.create` | create a own serviceAccount for the pod | `true` |
| `serviceAccount.name` | name of the serviceAccount to create | `""` | | `serviceAccount.name` | name of the serviceAccount to create | `""` |
| `podSecurityPolicy.create` | create a own PodSecurityPolicy for the pod | `false` | | `podSecurityPolicy.create` | create a own PodSecurityPolicy for the pod | `false` |
| `metrics.enabled` | create ServiceMonitor CR for Prometheus operator | `false` | | `metrics.enabled` | create ServiceMonitor CR for Prometheus operator | `false` |
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash ```bash
$ helm install --name my-release \ $ helm install --name my-release \
--set key_1=value_1,key_2=value_2 \ --set key_1=value_1,key_2=value_2 \
code-chris/cadvisor ckotzbauer/cadvisor
``` ```
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example, Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash ```bash
# example for staging # example for staging
$ helm install --name my-release -f values.yaml code-chris/cadvisor $ helm install --name my-release -f values.yaml ckotzbauer/cadvisor
``` ```
> **Tip**: You can use the default [values.yaml](values.yaml) > **Tip**: You can use the default [values.yaml](values.yaml)

View File

@ -1,14 +1,14 @@
apiVersion: v1 apiVersion: v1
description: nfs-client is an automatic provisioner that used your *already configured* NFS server, automatically creating Persistent Volumes. description: nfs-client is an automatic provisioner that used your *already configured* NFS server, automatically creating Persistent Volumes.
name: nfs-client-provisioner name: nfs-client-provisioner
version: 1.0.0 version: 1.0.1
appVersion: 3.1.0 appVersion: 3.1.0
home: https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client home: https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client
sources: sources:
- https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client - https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client
- https://github.com/code-chris/helm-charts - https://github.com/ckotzbauer/helm-charts
maintainers: maintainers:
- name: code-chris - name: ckotzbauer
email: christian.kotzbauer@gmail.com email: christian.kotzbauer@gmail.com
keywords: keywords:
- nfs - nfs

View File

@ -5,7 +5,7 @@ The [NFS client provisioner](https://github.com/kubernetes-incubator/external-st
## TL;DR; ## TL;DR;
```console ```console
$ helm install --set nfs.server=x.x.x.x --set nfs.path=/exported/path code-chris/nfs-client-provisioner $ helm install --set nfs.server=x.x.x.x --set nfs.path=/exported/path ckotzbauer/nfs-client-provisioner
``` ```
For **arm** deployments set `image.repository` to `--set image.repository=quay.io/external_storage/nfs-client-provisioner-arm` For **arm** deployments set `image.repository` to `--set image.repository=quay.io/external_storage/nfs-client-provisioner-arm`
@ -24,7 +24,7 @@ This charts installs custom [storage class](https://kubernetes.io/docs/concepts/
To install the chart with the release name `my-release`: To install the chart with the release name `my-release`:
```console ```console
$ helm install --name my-release --set nfs.server=x.x.x.x --set nfs.path=/exported/path code-chris/nfs-client-provisioner $ helm install --name my-release --set nfs.server=x.x.x.x --set nfs.path=/exported/path ckotzbauer/nfs-client-provisioner
``` ```
The command deploys the given storage class in the default configuration. It can be used afterswards to provision persistent volumes. The [configuration](#configuration) section lists the parameters that can be configured during installation. The command deploys the given storage class in the default configuration. It can be used afterswards to provision persistent volumes. The [configuration](#configuration) section lists the parameters that can be configured during installation.

View File

@ -1,16 +1,16 @@
apiVersion: v1 apiVersion: v1
description: Prometheus Blackbox Exporter description: Prometheus Blackbox Exporter
name: prometheus-blackbox-exporter name: prometheus-blackbox-exporter
version: 1.0.0 version: 1.0.1
appVersion: 0.16.0 appVersion: 0.16.0
home: https://github.com/prometheus/blackbox_exporter home: https://github.com/prometheus/blackbox_exporter
sources: sources:
- https://github.com/prometheus/blackbox_exporter - https://github.com/prometheus/blackbox_exporter
- https://github.com/code-chris/helm-charts - https://github.com/ckotzbauer/helm-charts
keywords: keywords:
- prometheus - prometheus
- blackbox - blackbox
- monitoring - monitoring
maintainers: maintainers:
- name: code-chris - name: ckotzbauer
email: christian.kotzbauer@gmail.com email: christian.kotzbauer@gmail.com

View File

@ -1,93 +1,93 @@
# Prometheus Blackbox Exporter # Prometheus Blackbox Exporter
Prometheus exporter for blackbox testing Prometheus exporter for blackbox testing
Learn more: [https://github.com/prometheus/blackbox_exporter](https://github.com/prometheus/blackbox_exporter) Learn more: [https://github.com/prometheus/blackbox_exporter](https://github.com/prometheus/blackbox_exporter)
## TL;DR; ## TL;DR;
```bash ```bash
$ helm install code-chris/prometheus-blackbox-exporter $ helm install ckotzbauer/prometheus-blackbox-exporter
``` ```
## Introduction ## Introduction
This chart creates a Blackbox-Exporter deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. This chart creates a Blackbox-Exporter deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
## Prerequisites ## Prerequisites
- Kubernetes 1.14+ with Beta APIs enabled - Kubernetes 1.14+ with Beta APIs enabled
## Installing the Chart ## Installing the Chart
To install the chart with the release name `my-release`: To install the chart with the release name `my-release`:
```bash ```bash
$ helm install --name my-release code-chris/prometheus-blackbox-exporter $ helm install --name my-release ckotzbauer/prometheus-blackbox-exporter
``` ```
The command deploys Blackbox Exporter on the Kubernetes cluster using the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. The command deploys Blackbox Exporter on the Kubernetes cluster using the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
## Uninstalling the Chart ## Uninstalling the Chart
To uninstall/delete the `my-release` deployment: To uninstall/delete the `my-release` deployment:
```bash ```bash
$ helm delete my-release $ helm delete my-release
``` ```
The command removes all the Kubernetes components associated with the chart and deletes the release. The command removes all the Kubernetes components associated with the chart and deletes the release.
## Configuration ## Configuration
The following table lists the configurable parameters of the Blackbox-Exporter chart and their default values. The following table lists the configurable parameters of the Blackbox-Exporter chart and their default values.
| Parameter | Description | Default | | Parameter | Description | Default |
| -------------------------------------- | ------------------------------------------------- | ----------------------------- | | -------------------------------------- | ------------------------------------------------- | ----------------------------- |
| `config` | Prometheus blackbox configuration | {} | | `config` | Prometheus blackbox configuration | {} |
| `secretConfig` | Whether to treat blackbox configuration as secret | `false` | | `secretConfig` | Whether to treat blackbox configuration as secret | `false` |
| `extraArgs` | Optional flags for blackbox | `[]` | | `extraArgs` | Optional flags for blackbox | `[]` |
| `extraConfigmapMounts` | Additional configmap mounts | `[]` | | `extraConfigmapMounts` | Additional configmap mounts | `[]` |
| `extraSecretMounts` | Additional secret mounts | `[]` | | `extraSecretMounts` | Additional secret mounts | `[]` |
| `image.repository` | container image repository | `prom/blackbox-exporter` | | `image.repository` | container image repository | `prom/blackbox-exporter` |
| `image.tag` | container image tag | `v0.15.1` | | `image.tag` | container image tag | `v0.15.1` |
| `image.pullPolicy` | container image pull policy | `IfNotPresent` | | `image.pullPolicy` | container image pull policy | `IfNotPresent` |
| `image.pullSecrets` | container image pull secrets | `[]` | | `image.pullSecrets` | container image pull secrets | `[]` |
| `ingress.annotations` | Ingress annotations | None | | `ingress.annotations` | Ingress annotations | None |
| `ingress.enabled` | Enables Ingress | `false` | | `ingress.enabled` | Enables Ingress | `false` |
| `ingress.hosts` | Ingress accepted hostnames | None | | `ingress.hosts` | Ingress accepted hostnames | None |
| `ingress.tls` | Ingress TLS configuration | None | | `ingress.tls` | Ingress TLS configuration | None |
| `nodeSelector` | node labels for pod assignment | `{}` | | `nodeSelector` | node labels for pod assignment | `{}` |
| `runAsUser` | User to run blackbox-exporter container as | `1000` | | `runAsUser` | User to run blackbox-exporter container as | `1000` |
| `readOnlyRootFilesystem` | Set blackbox-exporter file-system to read-only | `true` | | `readOnlyRootFilesystem` | Set blackbox-exporter file-system to read-only | `true` |
| `runAsNonRoot` | Run blackbox-exporter as non-root | `true` | | `runAsNonRoot` | Run blackbox-exporter as non-root | `true` |
| `tolerations` | node tolerations for pod assignment | `[]` | | `tolerations` | node tolerations for pod assignment | `[]` |
| `affinity` | node affinity for pod assignment | `{}` | | `affinity` | node affinity for pod assignment | `{}` |
| `podAnnotations` | annotations to add to each pod | `{}` | | `podAnnotations` | annotations to add to each pod | `{}` |
| `podDisruptionBudget` | pod disruption budget | `{}` | | `podDisruptionBudget` | pod disruption budget | `{}` |
| `priorityClassName` | priority class name | None | | `priorityClassName` | priority class name | None |
| `resources` | pod resource requests & limits | `{}` | | `resources` | pod resource requests & limits | `{}` |
| `restartPolicy` | container restart policy | `Always` | | `restartPolicy` | container restart policy | `Always` |
| `service.annotations` | annotations for the service | `{}` | | `service.annotations` | annotations for the service | `{}` |
| `service.labels` | additional labels for the service | None | | `service.labels` | additional labels for the service | None |
| `service.type` | type of service to create | `ClusterIP` | | `service.type` | type of service to create | `ClusterIP` |
| `service.port` | port for the blackbox http service | `9115` | | `service.port` | port for the blackbox http service | `9115` |
| `service.externalIPs` | list of external ips | [] | | `service.externalIPs` | list of external ips | [] |
| `serviceMonitors` | ServiceMonitor CRDs to create for prometheus operator | `[]` | | `serviceMonitors` | ServiceMonitor CRDs to create for prometheus operator | `[]` |
| `strategy` | strategy used to replace old Pods with new ones | `{"rollingUpdate":{"maxSurge":1,"maxUnavailable":0},"type":"RollingUpdate"}` | | `strategy` | strategy used to replace old Pods with new ones | `{"rollingUpdate":{"maxSurge":1,"maxUnavailable":0},"type":"RollingUpdate"}` |
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash ```bash
$ helm install --name my-release \ $ helm install --name my-release \
--set key_1=value_1,key_2=value_2 \ --set key_1=value_1,key_2=value_2 \
code-chris/prometheus-blackbox-exporter ckotzbauer/prometheus-blackbox-exporter
``` ```
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example, Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash ```bash
# example for staging # example for staging
$ helm install --name my-release -f values.yaml code-chris/prometheus-blackbox-exporter $ helm install --name my-release -f values.yaml ckotzbauer/prometheus-blackbox-exporter
``` ```
> **Tip**: You can use the default [values.yaml](values.yaml) > **Tip**: You can use the default [values.yaml](values.yaml)

View File

@ -1,17 +1,17 @@
apiVersion: v1 apiVersion: v1
description: Alertmanager Webhook for Microsoft Teams description: Alertmanager Webhook for Microsoft Teams
name: prometheus-msteams name: prometheus-msteams
version: 1.0.1 version: 1.0.2
appVersion: 1.3.3 appVersion: 1.3.3
home: https://github.com/bzon/prometheus-msteams home: https://github.com/bzon/prometheus-msteams
sources: sources:
- https://github.com/bzon/prometheus-msteams - https://github.com/bzon/prometheus-msteams
- https://github.com/code-chris/helm-charts - https://github.com/ckotzbauer/helm-charts
keywords: keywords:
- prometheus - prometheus
- msteams - msteams
- webhook - webhook
- alertmanager - alertmanager
maintainers: maintainers:
- name: code-chris - name: ckotzbauer
email: christian.kotzbauer@gmail.com email: christian.kotzbauer@gmail.com

View File

@ -1,81 +1,81 @@
# Prometheus MSTeams # Prometheus MSTeams
Alertmanager Webhook for Microsoft Teams Alertmanager Webhook for Microsoft Teams
Learn more: [https://github.com/bzon/prometheus-msteams](https://github.com/bzon/prometheus-msteams) Learn more: [https://github.com/bzon/prometheus-msteams](https://github.com/bzon/prometheus-msteams)
## TL;DR; ## TL;DR;
```bash ```bash
$ helm install code-chris/prometheus-msteams $ helm install ckotzbauer/prometheus-msteams
``` ```
## Introduction ## Introduction
This chart creates a Webhook deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. This chart creates a Webhook deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
## Prerequisites ## Prerequisites
- Kubernetes 1.9+ - Kubernetes 1.9+
## Installing the Chart ## Installing the Chart
To install the chart with the release name `my-release`: To install the chart with the release name `my-release`:
```bash ```bash
$ helm install --name my-release code-chris/prometheus-msteams $ helm install --name my-release ckotzbauer/prometheus-msteams
``` ```
The command deploys this Webhook on the Kubernetes cluster using the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. The command deploys this Webhook on the Kubernetes cluster using the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
## Uninstalling the Chart ## Uninstalling the Chart
To uninstall/delete the `my-release` deployment: To uninstall/delete the `my-release` deployment:
```bash ```bash
$ helm delete my-release $ helm delete my-release
``` ```
The command removes all the Kubernetes components associated with the chart and deletes the release. The command removes all the Kubernetes components associated with the chart and deletes the release.
## Configuration ## Configuration
The following table lists the configurable parameters of the Prometheus MSTeams chart and their default values. The following table lists the configurable parameters of the Prometheus MSTeams chart and their default values.
| Parameter | Description | Default | | Parameter | Description | Default |
| -------------------------------------- | ------------------------------------------------- | ----------------------------- | | -------------------------------------- | ------------------------------------------------- | ----------------------------- |
| `replicaCount` | Instance count to deploy | 1 | | `replicaCount` | Instance count to deploy | 1 |
| `image.repository` | container image repository | `bzon/prometheus-msteams` | | `image.repository` | container image repository | `bzon/prometheus-msteams` |
| `image.tag` | container image tag | `v1.1.5` | | `image.tag` | container image tag | `v1.1.5` |
| `image.pullPolicy` | container image pull policy | `IfNotPresent` | | `image.pullPolicy` | container image pull policy | `IfNotPresent` |
| `extraEnvs` | Optional env variables for webhook deployment | `[]` | | `extraEnvs` | Optional env variables for webhook deployment | `[]` |
| `nodeSelector` | node labels for pod assignment | `{}` | | `nodeSelector` | node labels for pod assignment | `{}` |
| `tolerations` | node tolerations for pod assignment | `[]` | | `tolerations` | node tolerations for pod assignment | `[]` |
| `affinity` | node affinity for pod assignment | `{}` | | `affinity` | node affinity for pod assignment | `{}` |
| `connectors` | MS Teams Connectors (URLs) | `{}` | | `connectors` | MS Teams Connectors (URLs) | `{}` |
| `customCardTemplate` | Customized template for Team cards | `""` | | `customCardTemplate` | Customized template for Team cards | `""` |
| `podAnnotations` | annotations to add to each pod | `{}` | | `podAnnotations` | annotations to add to each pod | `{}` |
| `additionalArgs` | additional container arguments | `[]` | | `additionalArgs` | additional container arguments | `[]` |
| `resources` | pod resource requests & limits | `{}` | | `resources` | pod resource requests & limits | `{}` |
| `service.type` | type of service to create | `ClusterIP` | | `service.type` | type of service to create | `ClusterIP` |
| `service.port` | port for the blackbox http service | `9115` | | `service.port` | port for the blackbox http service | `9115` |
| `service.externalIPs` | list of external ips | `[]` | | `service.externalIPs` | list of external ips | `[]` |
| `service.loadBalancerIP` | optional load balancer ip | `""` | | `service.loadBalancerIP` | optional load balancer ip | `""` |
| `service.loadBalancerSourceRanges` | optional load balancer source ranges | `[]` | | `service.loadBalancerSourceRanges` | optional load balancer source ranges | `[]` |
| `service.externalTrafficPolicy` | optional external traffic policy | `""` | | `service.externalTrafficPolicy` | optional external traffic policy | `""` |
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash ```bash
$ helm install --name my-release \ $ helm install --name my-release \
--set key_1=value_1,key_2=value_2 \ --set key_1=value_1,key_2=value_2 \
code-chris/prometheus-msteams ckotzbauer/prometheus-msteams
``` ```
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example, Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash ```bash
# example for staging # example for staging
$ helm install --name my-release -f values.yaml code-chris/prometheus-msteams $ helm install --name my-release -f values.yaml ckotzbauer/prometheus-msteams
``` ```
> **Tip**: You can use the default [values.yaml](values.yaml) > **Tip**: You can use the default [values.yaml](values.yaml)