kube-state-metrics has a collector for each kind of Kubernetes resource
it collects metrics from. Each of those collectors directly influences
the RBAC requirements for the Pods. Additionally due to the nature of
how kube-state-metrics is versioned and released it is not easy to
determine which collectors are using "alpha" APIs, which are not
necessarily enabled in a cluster, but kube-state-metrics by default has
all collectors enabled.
* Add support for using an external Cassandra or ElasticSearch backing store.
* Update README for deploying with a new ES cluster
* Updated portions of the readme
* Update if statements to make more readable
* Chart details for Riemann
Riemann is a stream based metric processing engine.
* First draft of the README
* Move the riemann website link
* Added a livenessProbe
* Remove trailing whitespace
* Namespace the helper templates.
Feedback from https://github.com/kubernetes/charts/pull/2652
* Probes should use exposed container port values.
Oops. I got too cute using .Values here and was using the service
values. The liveness and readiness probes must be pointed at exposed
container ports.
Port 5555 is exposed in the image via `EXPOSE 5555`, but I have also
explicitly exposed it via a containers.ports.containerPort entry.
* Rename the configMap to follow standard naming.
* Added missing standard labels
* Separate the image and tag values
* Switch to named ports for service/pod communication
Naming the container ports and referencing those in the service is much
easier and cleaner.
* Use my github name
* Fix formatting
If lines were indented weird. New Output:
spec:
type: ClusterIP
ports:
- name: riemann-tcp
port: 5555
targetPort: riemann-tcp
protocol: TCP
- name: riemann-udp
port: 5555
targetPort: riemann-udp
protocol: UDP
- name: riemann-ws
port: 5556
targetPort: riemann-ws
protocol: TCP
* jasperreports: update to `bitnami/jasperreports:6.4.2-r0`
* jasperreports: bump chart appVersion to `6.4.2`
* jasperreports: bump chart version to `0.2.1`
* moodle: update to `bitnami/moodle:3.4.0-r0`
* moodle: bump chart appVersion to `3.4.0`
* moodle: bump chart version to `0.3.2`
* Fixed missing space in yaml comment after #
* phabricator: update to `bitnami/phabricator:2017.45.0-r0`
* phabricator: bump chart appVersion to `2017.45.0`
* phabricator: bump chart version to `0.4.27`
The previous version of the sync script ran `helm dep update` which
would recreate the requirements.lock file. This caused new builds
of charts as a total package with different versions of dependencies
but the same chart version. The package was mutating.
This change works towards our goal of immutable charts for a chart
at a version.
* Update redis image
* delete blank lines
* fix chart version
* delete tailing spaces
* new line
* new line character in the end
* fix persistance volume claim | pvc was pointing to a wrong claim
* add image repos in chart's sources
* Create 2 PVC for Master and slave components and update Slave deployment to Statefulset
* bump to version 0.3.0
* Update Chart version --> 1.0.0
* Fix typo
The uses a configurable template value for the name parameter of the pvc
section of the data and master statefulset templates. The default is set
to `data` and so remains unchanged to any dependent user.
A little background: We currently have a production ES cluster using a
locally maintained elasticsearch chart and we want to migrate to using
this chart. A blocker at the moment is that our pvc name is `storage`
instead of `data`. To avoid needing to create a new cluster (which is
close to a TB in storage) and migrating, we can simply set this
parameter to `storage` and we can continue to use the pvc currently in
place.