* Put S3 keys into Secret and allow specifying an existing secret for that
Signed-off-by: Gert-Jan van Ginkel <gertjanvg@gmail.com>
* [stable/sentry] Version bump
Signed-off-by: Gert-Jan van Ginkel <gertjanvg@gmail.com>
* Update Postgres depenency
The chart has been updated a lot, since we've introduced that
dependency.
It mainly introduces new version of Postgres and doesn't seem to break
the general functionality. It does introduce some template changes and
fixes a single problem, where policy has an empty value and causes
kubernetes to fall out in persistant volume claim.
```yaml
annotations:
"helm.sh/resource-policy":
```
Signed-off-by: Rafal Proszowski <rafal.proszowski@digital.cabinet-office.gov.uk>
* Upgrade Redis chart
We're simply running an old version, and it may be a pain to upgrade
later in the future.
Signed-off-by: Rafal Proszowski <rafal.proszowski@digital.cabinet-office.gov.uk>
* Add support for overwritten naming
It may be a case, when a user would like to install two different
instances of postgres or redis in the same namespace with a single
release. This would cause one of the instances being overwritten by the
other and lead to unwanted behaviour.
Adding this support and prefixing sentry's dependencies, may solve that
problem, and doesn't really strike as a bad practice.
Signed-off-by: Rafal Proszowski <rafal.proszowski@digital.cabinet-office.gov.uk>
* Bump sentry chart version
Signed-off-by: Rafal Proszowski <rafal.proszowski@digital.cabinet-office.gov.uk>
* Update configmap to match sentry
Update configmap to match the latest version from sentry
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Include google auth in mapping
Include google auth when mapping env variables
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Bump Senty version
Bump sentry version from 9.1.1 to 9.1.2, No breaking changes.
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Bump chart version
Bump the version from 3.0.1 to 3.0.2
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Correct wrong parenthesis in google client config
Fix Wrong placed parenthesis for Google client id to sync with local changes.
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Use single quotes to match the config style
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Remove duplication in File storage
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Handle mail server manually
To ensure the existence of default values.
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
* Config Mail Server in the old way.
To avoid index out of range in sentry
Signed-off-by: Ahmed Magdy <ahmedmagdi@outlook.com>
Added the default memory limit for db-init-hook refs #15296
Added a warning related to changing default memory limit for db-init-hook
Signed-off-by: Mikhail Naletov <okgolove@markeloff.net>
* [stable/sentry] provide greater coverage of filestore settings
This stemmed primarily from needing to inject a Google Cloud service account into
the filesystem via a secret. However it seemed sensible if adding support for one
of the additional filestore providers to add support for both.
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [sentry/stable] document the change in parameters around filestore
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [stable/sentry] Bump chart version to 2.0.0
values.yaml changed in a breaking way, so a major version bump seems prudent.
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [stable/sentry] change s3 from commented out to empty block
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [stable/sentry] correct the values reference for persistentWorkers
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [stable/sentry] change /var/secrets to /var/run/secrets
Use the same path format as the Kubernetes default service account to
place the service account key for GCS storage.
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [stable/sentry] update path for GCS key in comment in values.yaml
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [stable/sentry] correct filesystem path key for mountPath
Signed-off-by: Damien Churchill <damoxc@gmail.com>
* [stable/sentry] add note in README about the value keys which have changed
Signed-off-by: Damien Churchill <damoxc@gmail.com>
This PR adds a note to the readme stating that the chart is not maintained or backed by Sentry org itself.
Signed-off-by: Burak Yigit Kaya <byk@sentry.io>
* Mount persistent volume into cron and worker
Signed-off-by: Robert de Vries <r.devries@robbytu.net>
* Bump Sentry chart version
Signed-off-by: Robert de Vries <r.devries@robbytu.net>
* Add existingClaim to default values
Signed-off-by: Robert de Vries <r.devries@robbytu.net>
* Add the persistentWorkers option to mount PVC to cron and worker deployments
Signed-off-by: Robert de Vries <r.devries@robbytu.net>
* Updated persistence documentation in README
Signed-off-by: Robert de Vries <r.devries@robbytu.net>
This will cleanup the db init and user create job if they succeed. It will also delete them if the install fails and you run install again, that way new db init and user create jobs will run again.
Signed-off-by: Todd Brown <mrbrownt@me.com>
* Adding support for labels to overcome redis network restrictions
Signed-off-by: Matthew Green <matthew@newedgeengineering.com>
* bump version number, recover from accidental push
Signed-off-by: Matthew Green <matthew@newedgeengineering.com>
