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
[![](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]: 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
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
- [cadvisor](https://github.com/code-chris/helm-charts/tree/master/charts/cadvisor)
- [nfs-client-provisioner](https://github.com/code-chris/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-msteams](https://github.com/code-chris/helm-charts/tree/master/charts/prometheus-msteams)
- [cadvisor](https://github.com/ckotzbauer/helm-charts/tree/master/charts/cadvisor)
- [nfs-client-provisioner](https://github.com/ckotzbauer/helm-charts/tree/master/charts/nfs-client-provisioner)
- [prometheus-blackbox-exporter](https://github.com/ckotzbauer/helm-charts/tree/master/charts/prometheus-blackbox-exporter)
- [prometheus-msteams](https://github.com/ckotzbauer/helm-charts/tree/master/charts/prometheus-msteams)

View File

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

View File

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

View File

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

View File

@ -5,7 +5,7 @@ The [NFS client provisioner](https://github.com/kubernetes-incubator/external-st
## TL;DR;
```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`
@ -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`:
```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.

View File

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

View File

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

View File

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

View File

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