1
0
Fork 0
mirror of https://github.com/prometheus-operator/prometheus-operator.git synced 2025-04-21 11:48:53 +00:00

add make helm-init-repo command to initialize the helm repo …

Move all exporters to the helm root folder
Add make helm-init-repo command to initialize the helm repo
This commit is contained in:
Giancarlo Rubio 2017-11-12 11:03:37 +01:00 committed by Antoine Legrand
parent 0862eb7312
commit e456b2fabf
80 changed files with 69 additions and 53 deletions

View file

@ -7,6 +7,7 @@ PROMU := $(GOPATH)/bin/promu
PREFIX ?= $(shell pwd)
pkgs = $(shell go list ./... | grep -v /vendor/ | grep -v /test/)
HELM_BUCKET_NAME=coreos-charts
all: check-license format build test
@ -77,4 +78,16 @@ jsonnet:
jsonnet-docker:
docker build -f scripts/jsonnet/Dockerfile -t po-jsonnet .
helm-package:
mkdir -p /tmp/helm
(cd $(CURDIR)/helm && helm package $(HELM_PACKAGES) -d /tmp/helm && cd -)
helm repo index /tmp/helm --url https://s3-eu-west-1.amazonaws.com/$(HELM_BUCKET_NAME)/stable/ --debug
aws s3 sync --acl public-read /tmp/helm/ s3://$(HELM_BUCKET_NAME)/stable/
helm-packages:
make helm-package HELM_PACKAGES=exporter-*
make helm-package HELM_PACKAGES="alertmanager grafana prometheus prometheus-operator"
(cd $(CURDIR)/helm/'kube-prometheus' && helm dep update && cd -)
make helm-package HELM_PACKAGES='kube-prometheus'
.PHONY: all build crossbuild test format check-license container e2e-test e2e-status e2e clean-e2e embedmd apidocgen docs

View file

@ -7,4 +7,4 @@ maintainers:
name: alertmanager
sources:
- https://github.com/coreos/prometheus-operator
version: 0.0.4
version: 0.0.5

View file

@ -5,7 +5,8 @@ Installs a [Prometheus](https://prometheus.io) Alertmanager instance using the C
## TL;DR;
```console
$ helm install opsgoodness/alertmanager
$ helm repo add coreos https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
$ helm install coreos/alertmanager
```
## Introduction
@ -21,7 +22,7 @@ This chart bootstraps an [Alertmanager](https://github.com/prometheus/alertmanag
To install the chart with the release name `my-release`:
```console
$ helm install opsgoodness/alertmanager --name my-release
$ helm install coreos/alertmanager --name my-release
```
The command deploys Alertmanager on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
@ -64,13 +65,13 @@ Parameter | Description | Default
`storageSpec` | Alertmanager StorageSpec for persistent data | `{}`
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
$ helm install opsgoodness/alertmanager --name my-release --set externalUrl=http://alertmanager.example.com
$ helm install coreos/alertmanager --name my-release --set externalUrl=http://alertmanager.example.com
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install opsgoodness/alertmanager --name my-release -f values.yaml
$ helm install coreos/alertmanager --name my-release -f values.yaml
```
> **Tip**: You can use the default [values.yaml](values.yaml)

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart for Kubernetes
name: exporter-kube-api
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart for Kubernetes
name: exporter-kube-controller-manager
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart singleton for kube-state-metrics
name: exporter-kube-dns
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart for Kubernetes
name: exporter-kube-etcd
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart singleton for kube-state-metrics
name: exporter-kube-scheduler
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart singleton for kube-state-metrics
name: exporter-kube-state
version: 0.1.2
version: 0.1.3
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart for Kubernetes
name: exporter-kubelets
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart for Kubernetes
name: exporter-kubernetes
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -1,7 +1,7 @@
apiVersion: v1
description: A Helm chart for Kubernetes
name: exporter-node
version: 0.1.0
version: 0.1.1
maintainers:
- name: Cloud Posse LLC
email: hello@cloudposse.com

View file

@ -6,4 +6,4 @@ maintainers:
name: grafana
sources:
- https://github.com/coreos/prometheus-operator
version: 0.0.3
version: 0.0.4

View file

@ -5,7 +5,8 @@
## TL;DR;
```console
$ helm install opsgoodness/grafana
$ helm repo add coreos https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
$ helm install coreos/grafana
```
## Introduction
@ -16,7 +17,7 @@ This chart bootstraps an [Grafana](http://grafana.org) deployment on a [Kubernet
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release opsgoodness/grafana
$ helm install --name my-release coreos/grafana
```
## Uninstalling the Chart
@ -56,13 +57,13 @@ Parameter | Description | Default
`storageSpec` | Grafana StorageSpec for persistent data | `{}`
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
$ helm install opsgoodness/grafana --name my-release --set adminUser=bob
$ helm install coreos/grafana --name my-release --set adminUser=bob
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install opsgoodness/grafana --name my-release -f values.yaml
$ helm install coreos/grafana --name my-release -f values.yaml
```
> **Tip**: You can use the default [values.yaml](values.yaml)

View file

@ -1,45 +1,45 @@
dependencies:
- name: alertmanager
version: 0.0.3
repository: http://charts.opsgoodness.com
version: 0.0.5
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: prometheus
version: 0.0.3
repository: http://charts.opsgoodness.com
version: 0.0.5
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kube-api
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kube-controller-manager
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kube-dns
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kube-etcd
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kube-scheduler
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kube-state
version: 0.1.2
repository: https://charts.cloudposse.com/incubator
version: 0.1.3
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kubelets
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-kubernetes
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
- name: exporter-node
version: 0.1.0
repository: https://charts.cloudposse.com/incubator
version: 0.1.1
repository: https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
condition: deployExporterNode

View file

@ -7,4 +7,4 @@ maintainers:
name: prometheus-operator
sources:
- https://github.com/coreos/prometheus-operator
version: 0.0.6
version: 0.0.7

View file

@ -5,8 +5,8 @@ Installs [prometheus-operator](https://github.com/coreos/prometheus-operator) to
## TL;DR;
```console
$ helm repo add opsgoodness http://charts.opsgoodness.com
$ helm install opsgoodness/prometheus-operator
$ helm repo add coreos https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
$ helm install coreos/prometheus-operator
```
## Introduction
@ -56,7 +56,7 @@ $ helm init --service-account tiller
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release opsgoodness/prometheus-operator
$ helm install --name my-release coreos/prometheus-operator
```
The command deploys prometheus-operator on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
@ -97,13 +97,13 @@ Parameter | Description | Default
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release opsgoodness/prometheus-operator --set sendAnalytics=true
$ helm install --name my-release coreos/prometheus-operator --set sendAnalytics=true
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release opsgoodness/prometheus-operator -f values.yaml
$ helm install --name my-release coreos/prometheus-operator -f values.yaml
```
> **Tip**: You can use the default [values.yaml](values.yaml)

View file

@ -22,7 +22,7 @@ configmapReload:
##
image:
repository: quay.io/coreos/prometheus-operator
tag: v0.13.0
tag: v0.14.1
pullPolicy: IfNotPresent
## If enabled, prometheus-operator will create a service for scraping kubelets

View file

@ -7,4 +7,4 @@ maintainers:
name: prometheus
sources:
- https://github.com/coreos/prometheus-operator
version: 0.0.4
version: 0.0.5

View file

@ -5,7 +5,8 @@ Installs a [Prometheus](https://prometheus.io) instance using the CoreOS [promet
## TL;DR;
```console
$ helm install opsgoodness/prometheus
$ helm repo add coreos https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
$ helm install coreos/prometheus
```
## Introduction
@ -21,7 +22,7 @@ This chart bootstraps a [Prometheus](https://github.com/prometheus/prometheus) d
To install the chart with the release name `my-release`:
```console
$ helm install opsgoodness/prometheus --name my-release
$ helm install coreos/prometheus --name my-release
```
The command deploys Prometheus on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
@ -73,13 +74,13 @@ Parameter | Description | Default
`storageSpec` | Prometheus StorageSpec for persistent data | `{}`
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
$ helm install opsgoodness/prometheus --name my-release --set externalUrl=http://prometheus.example.com
$ helm install coreos/prometheus --name my-release --set externalUrl=http://prometheus.example.com
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example:
```console
$ helm install opsgoodness/prometheus --name my-release -f values.yaml
$ helm install coreos/prometheus --name my-release -f values.yaml
```
> **Tip**: You can use the default [values.yaml](values.yaml)