forked from timescale/helm-charts
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebasing Fork with Upstream #2
Open
klaus385
wants to merge
209
commits into
master
Choose a base branch
from
timescale-main
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
charts: deprecate loadbalancer SVCs
Fix regexp in renovate configuration
Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
chore(deps): update dependency timescale/promscale to v0.16.0
charts/promscale: regenerate alerts
Previous setting collided with our processes related to issues management and caused unnecessary notifications.
.github: do not close dependency dashboard issue
Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
Signed-off-by: Arunprasad Rajkumar <[email protected]> Signed-off-by: Arunprasad Rajkumar <[email protected]>
chart/avalanche: add options related to pod placing
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
The field for target labels in a PodMonitor spec is called [podTargetLabels](https://github.com/prometheus-operator/prometheus-operator/blob/main/pkg/apis/monitoring/v1/types.go\#L1330). The `targetLabels` field only exists for service monitors.
…ale#490) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Cleanup deprecated code
…es_exporter Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
Update prometheus rule for Promscale chart
Currently we use k8s StatefulSet and native replica to create multiple Avalanche instances to generate series load to Prometheus. However this is less optimal and occupies real CPU & memory in a benchmarking environment. This fix creates fake Service to mimic existence of multiple avalanche with less demanding resources. A new helm value `fakePrometheusTargetCount` has been introduced to declare the number of fake prometheus targets to be created for avalanche. Signed-off-by: Arunprasad Rajkumar <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Signed-off-by: 0xffox <[email protected]>
Signed-off-by: 0xffox <[email protected]>
This commit allows to configure scrapeTimeout for Prometheus instances. This is particularly useful in benchmarks when scraping large targets with > 2M series, since then Prometheus needs more than 10s (default `scrapeTimeout`) to complete. Signed-off-by: Harkishen Singh <[email protected]>
* Note to enable backup for the restored release In order to enable backup on the restored release, we have to enable backup section and disable boostrap from backup section in helm value and upgrade the release. Signed-off-by: naveenkumarsp <[email protected]> * Update Chart.yaml Bumping the chart version Signed-off-by: naveenkumarsp <[email protected]> * Bumping the chart version to 0.27.3 Signed-off-by: naveenkumarsp <[email protected]> * bump chart version Signed-off-by: naveenkumarsp <[email protected]> Co-authored-by: Paweł Krupa <[email protected]>
Signed-off-by: alejandrodnm <[email protected]>
Signed-off-by: David Andreoletti <[email protected]>
Signed-off-by: David Andreoletti <[email protected]>
Adding topologySpreadConstraints and removing `affinityTemplate` to allow easier handling of topology spread. Defaulting to kubernetes defaults when it comes to handling topology Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
…ale#548) * chore(deps): update dependency timescale/promscale to v0.17.0 * charts/promscale: bump major version Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Paweł Krupa (paulfantom) <[email protected]>
… number for patroni reloader job Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* add pgbackrest-secrets for gcs service key * add documentation for backing up to gcs * clean up gcs backup documentation and fix example * revert autogenerated toc changes * check for empty pgbackrest secret (for gcs) * remove s3 defaults and add examples for backup providers * add documentation for s3 azure and gcs changes * Fixed linting error * bump chart version * remove trailing space Signed-off-by: Gunnar Sundberg <[email protected]> Co-authored-by: Alex Grönholm <[email protected]>
… schemas, add icon to remove helm lint warning (timescale#558)
* set patronictl config file * bump chart version * revert line removal
* fix issue with global/local scope * bump version (patch)
Signed-off-by: Ramon Guiu <[email protected]>
Signed-off-by: Ramon Guiu <[email protected]>
* Revert "Merge pull request timescale#588 from timescale/update-semver-mathis" This reverts commit dd4db38, reversing changes made to 8484516. * Fix helm release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updating my fork with recent upstream commits while preserving my changes.