* Update Keycloak to 4.0.0.Final
* Add support for MariaDB and H2
* Make H2 the default for easy testing
* Make CI test the chart with H2 and a HA setup with Postgres
Fixes: #6151
* Similar to other charts, this allows configurable name
overrides so 'cleaner' resource names can be achieved,
which are independent from the wanted release names.
* This is a must have if you want to integrate influxdb with
other charts, where a resource name can't be templated
and has to be fixed in the values.yaml, and you have to
deploy that in multiple instances on the same k8s cluster.
For example if you have an integration chart and
the grafana data source URI points to a fixed influxdb
service name, then without this patch,
it can't be deployed in multiple instances,
since the service name depends on the release name,
which has to be unique.
* Detect allocation without using JQ
* increase chart version
* Add post-start-hook to clean up deallocation node
* Add missing post-start-hook.sh life cycle
* Increase chart version to resolve build failed
* Bump chart version
And include myself as maintainer, nyah!
* Update the README
Include links to the vault and vault operator helm charts
* Make the `ConfigMap` more mappy
* Update the Goldfish values
* Use the "official" Goldfish image
And update the deployment to consume the config/token from environment variables.
* Empty vault token by default
So Goldfish doesn't attempt bootstrapping
* Empty vault token by default
Otherwise e2e goes 💥
* Fix maintainer names
* Chance the `pullPolicy`
Revert from `Always` back to `IfNotPresent`
[Elastic APM](https://www.elastic.co/guide/en/apm/get-started/current/overview.html) is an application performance monitoring system built on the Elastic Stack. This chart is to install the server part of the system.
See the official documentation to setup the agent part of the system.
Even though apm-server is built by the Elastic team, it supports alternative outputs other than Elasticsearch via built-in beat output plugins and community plugins. For example, [awsbeats](https://github.com/s12v/awsbeats) enables apm-server to write collected application traces to AWS Kinesis Streams.
Other changelog:
- Include the commented-out elasticsearch output too support common use-cases
- Include the configuraion table in the README
Manually verified to work by installing it like `helm install ~/charts/stable/heartbeat --name hb --namespace hb` and then reading logs:
```console
$ stern --namespace hb heart
+ hb-heartbeat-zljn2 › heartbeat
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:17.531ZINFOinstance/beat.go:468Home path: [/usr/share/heartbeat] Config path: [/usr/share/heartbeat] Data path: [/usr/share/heartbeat/data] Logs path: [/usr/share/heartbeat/logs]
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:17.532ZINFOinstance/beat.go:475Beat UUID: cc04f1e7-c1a2-4e9c-beca-009539becd87
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:17.532ZINFOinstance/beat.go:213Setup Beat: heartbeat; Version: 6.2.4
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.534ZINFOadd_cloud_metadata/add_cloud_metadata.go:297add_cloud_metadata: hosting provider type not detected.
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.534ZINFOfileout/file.go:76Initialized file output. path=/usr/share/heartbeat/data/heartbeat max_size_bytes=10240000 max_backups=5 permissions=-rw-------
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.535ZINFOpipeline/module.go:76Beat name: hb-heartbeat-zljn2
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.535ZWARNbeater/heartbeat.go:24Beta: Heartbeat is beta software
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.535ZINFObeater/manager.go:110Select (active) monitor icmp
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.537ZINFO[monitoring]log/log.go:97Starting metrics logging every 30s
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.538ZINFOinstance/beat.go:301heartbeat start running.
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:20.538ZINFObeater/heartbeat.go:56heartbeat is running! Hit CTRL-C to stop it.
hb-heartbeat-zljn2 heartbeat 2018-05-25T09:07:50.538ZINFO[monitoring]log/log.go:124Non-zero metrics in the last 30s{"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":40,"time":40},"total":{"ticks":70,"time":74,"value":70},"user":{"ticks":30,"time":34}},"info":{"ephemeral_id":"23539714-a27c-40bb-a124-805b7e009958","uptime":{"ms":33026}},"memstats":{"gc_next":4194304,"memory_alloc":2423104,"memory_total":4047776,"rss":22454272}},"libbeat":{"config":{"module":{"running":0}},"output":{"events":{"acked":5,"batches":5,"total":5},"type":"file","write":{"bytes":2306}},"pipeline":{"clients":1,"events":{"active":1,"published":6,"total":6},"queue":{"acked":5}}},"system":{"cpu":{"cores":2},"load":{"1":0.75,"15":0.38,"5":0.55,"norm":{"1":0.375,"15":0.19,"5":0.275}}}}}}
```
Templates and values.yaml is mostly similar to stable/filebeat's.
The main difference is `config:` in values.yaml, which directly reflects heartbeat's own configuration file.
Other changelog:
- Include the configuration table in README
- Include the commented-out elasticsearch output to support common use-cases
* Replicaset Prometheus Metrics export
* bugfix: Fix TLS issues
1. Moves context of ssl configuration script into /work-dir
where certain files are expected to be created.
2. Specifies the --sslMode=requireSSL flag on the container command when using TLS
as specified by mongo docs.
https://docs.mongodb.com/manual/tutorial/configure-ssl/
* Documentation on metrics options
* Bump Chart Version
* Add Version to 0.1.1
Add Version to 0.1.1
* [stable/distributed-tensorflow]Typo fix tables lists->table lists
[stable/distributed-tensorflow]Typo fix tables lists->table lists
* Fix sentry-kubernetes
in #5952 I added sentry.environment and sentry.release values, but for
sentry.values, we used to use the k8s metadata information to fill this value. Unfortunately this causes an error when deploying the chart, *I think* this value isn't available until the chart is deployed? Anyway upon further reflection I can't think of a good usecase for passing the RELEASE value. (Atleast its not required for my usecase)
So this just removes the problem value set
* add conditional
* add RBAC resources
For clusters with a PodSecurityPolicy admission controller, every pod
must have an associated PodSecurityPolicy to be scheduled.
* fix incorrect version bump
* add RBAC resources
for clusters with the PodSecurityPolicy admission controller, every pod
must have an associated PodSecurityPolicy
* remove unneeded PVC permission
* re-bump version
Reinhard Nägele
Chr1st0ph
David J. M. Karlsen
Bitnami Bot
Viktor Petersson
AdamDang
Richard Alberto
Ferenc-
lightnet328
Cédric de Saint Martin
Xavier Vello
Gianluca Bortoli
Ganesh S Patil
Teppei Fukuda
Christoph Hösler
Marcos Estévez Martínez
Siri
Michael Laccetti
KUOKA Yusuke
Salim Salaues
b13n1u
Giancarlo Rubio
Cornelius Keller
Jakub Borys
Anatoli Iariomenco
Aaron Mell
Atsushi Kawamura
Rafael Ríos Saavedra
wwojcik
Craig Mulligan
Alen Komljen
Naoki Ainoya
Kevin Lefevre
Brian Thorne
Raffael Schmid
Chih-Chieh
Michael Raimondi