* If you do not specify a retention time then by default it is set to 15 days.
In this PR I make that the default so that its clear to users.
Signed-off-by: David O'Dell <dave@helix.re>
* bumped chart version
Signed-off-by: David O'Dell <dave@helix.re>
* rev'd chart version to 8.11.5
Signed-off-by: David O'Dell <dave@helix.re>
* [stable/heapster] fix how to define fullname
This follows the default _helpers.tpl by `helm create NAME`
Signed-off-by: Shoichi Kaji <skaji@cpan.org>
* [stable/heapster] 0.3.3 -> 0.3.4
Signed-off-by: Shoichi Kaji <skaji@cpan.org>
* [stable/heapster] This will be a breaking change so we should up it by a major version
Signed-off-by: Shoichi Kaji <skaji@cpan.org>
This parameter can be useful if we want to supply the access keys via an
external secret. This should work with any cloud provider.
In my case I don't want to authorize the workers to interact with the ASG,
as any container running in the cluster would be allowed to do so,
instead I have created an IAM user and stored the credentials in a
secret.
Signed-off-by: Alessandro Siragusa <alessandro.siragusa@gmail.com>
* Allow specifying a securityContext
This enables users running under restrictive PodSecurityPolicies to deploy the exporter running as a non-root container.
Signed-off-by: Dimitrios Karagiannis <dhkarag@gmail.com>
* Update chart version
Signed-off-by: Dimitrios Karagiannis <dhkarag@gmail.com>
* [stable/redis-ha] Improve liveness probe so that redis is not restarted while it is still loading its dataset into memory
On larger databases this can take more than just the initial probe delay. During this time redis will not answer the ping command with pong, but with loading. Of course the container should not be marked as ready, but it also should not restart which results in redis never starting successfully.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
* [stable/redis-ha] Bump version to 3.5.2
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
* define prometheus exporter port in service
This enables prometheus-operator to work with this chart almost out-of-the box. Only a ServiceMonitor definition is necessary.
Signed-off-by: Ben Dimbeck <bd@it-agenten.com>
* bump chart version
Signed-off-by: Ben Dimbeck <bd@it-agenten.com>
* [stable/prometheus-operator] Allow template strings in metricRelabelings
This allows passing template strings as follows to do things such as
only keeping metrics for the current namespace
```
metricRelabelings:
- sourceLabels:
- namespace
regex: '{{ .Release.Namespace }}'
action: keep
```
Signed-off-by: Robbie deMuth <robbie.demuth@appian.com>
* [stable/prometheus-operator] Disable AlertManager connection when AlertManager is disabled
Previously, the Prometheus server was still wired to the default
AlertManager server even when `.Values.alertmanager.enabled` was set to
`false`
Signed-off-by: Robbie deMuth <robbie.demuth@appian.com>
* [stable/prometheus-operator] Allow template strings in Alertmanager configuration directives
This allows passing template strings as follows to do things such as
configure a webhook_config URL to point to a service deployed in the
same namespace
```
alertmanager:
config:
receivers:
- name: webhook
webhook_configs:
- url: http://alertmanager-webhook.{{ .Release.Namespace }}.svc.cluster.local/
```
Signed-off-by: Robbie deMuth <robbie.demuth@appian.com>
* [stable/prometheus-operator] Increment chart version
Signed-off-by: Robbie deMuth <robbie.demuth@appian.com>
* [stable/ambassador] Adding in additional TCP Port support for use with TCPMappings
Signed-off-by: Matt Christiansen <mchristiansen@exabeam.com>
* Changing version to minor version
Signed-off-by: Matt Christiansen <mchristiansen@exabeam.com>
* Allow to add more secrets
Allow to add an then mount secrets
For example certficates
Signed-off-by: Pawel Kalemba <pawel.kalemba@corp.ovh.com>
* Lint code ,add space as requested
Signed-off-by: Pawel Kalemba <pawel.kalemba@corp.ovh.com>
* [stable/spinnaker] fix bug where spinnaker can't connect to minio
As reported in spinnaker itself [here](https://github.com/spinnaker/spinnaker/issues/4431),
It doesn't appear to affect the current stable build, but it has problems with the nightly builds.
This change should innoculate us from that bug if it makes it through to a stable build.
Effectively the issue is that in the newer builds of spinnaker it attempts to use domain paths
for s3 access. This means instead of trying to connect to `spinnaker-minio/spinnaker` which should
be valid dns for the minio service it tries to connect to `spinnaker.spinnaker-minio` and fails because
this is not valid dns for minio.
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
* bump halyard version for cli arg needed
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
* fix argument
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
* fix version
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
* Add security context for default backend, remove nginx sa on default backend, update readme
Signed-off-by: LucasBoisserie <lucas.boisserie@gmail.com>
* Bump version
Signed-off-by: LucasBoisserie <lucas.boisserie@gmail.com>
* use run user at container level
Signed-off-by: LucasBoisserie <lucas.boisserie@gmail.com>