This repository was archived by the owner on Jan 11, 2024. It is now read-only.
[DATA-6011] Upgrade 0.9.2 #3
Merged
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
* feat(helm): add pod annotations to jobs * feat(helm): add pod annotation to cron jobs. * docs(helm): Add podAnnotation documentation and default values. * feat(helm) chart version bump.
* <feat>(datahub-frontend): Allow lifecycle hooks This PR adds a lifecycle node to the datahub-frontend deployment template. It can be used to execute lifecycle hooks, e.g. postStart actions, like replacing the default user.props file. * Bump chart version to 0.2.86 Co-authored-by: Pedro Silva <pedro.cls93@gmail.com>
* <feat>(datahub-upgrade): Restore Indices Resources This PR adds the ability for end-users to specify resource requests and limits for the datahub upgrade job 'restore indices'. This is needed for situations where the restore indices job will OOM due to a large backfill of data. I've seen this happening with our deployment of datahub and am unable to tune the resources for the restore indices job because the current requests and limits are hard-coded.
* fix(gms): remove unused JMX sidecar in favour of the already included JVM agent * Update Chart.yaml * Update Chart.yaml
…optional dependency (acryldata#121)
…es needed in ingestion recipes (acryldata#169) * Mount a customer defined k8s secret for ssl secrets needed in ingestion recipes * Bump chart versions * Address comment * Update readme * Address Pedro's comment
…ryldata#170) * Add kafka-exporter to expose prometheus metrics for kafka cluster * Kafka-exporter: Updated values.yaml to support tls/sasl authentication while connecting kafka cluster * Kafka-exporter: Updated values.yaml to remove default values and correct intendation * Add kafka-exporter to expose prometheus metrics for kafka cluster * Kafka-exporter: Updated values.yaml to support tls/sasl authentication while connecting kafka cluster * Kafka-exporter: Updated values.yaml to remove default values and correct intendation * Updated chart version
* bumping to 0.8.45 * Fixing
…ces (acryldata#181) * feat(frontend): add service monitoring * feat(gms): add service monitoring * gms: servicemonitor * feat(mae): enable service monitoring * update READMEs * fix service ports * bump version * Add missing default value * Update charts/datahub/Chart.yaml * delete jmx config and rename port to http
…t boot (acryldata#180) * fix(auth-secret): Make template use correct retrieval method `datahub-auth-secret` yaml was incorrectly using the `index` template function which is for list variables. For dictionaries as is the case with the `$secret.data` object, the correct method is: https://helm.sh/docs/chart_template_guide/function_list/#get Tested locally, that this works against a running cluster. * Updates encryption secret to use get helm function * feat(secrets): Allow users to specify their own secret values at first boot
* fix(datahub-frontend): Remove unused env var * Bump chart version
…ata#185) * feat(release): automatically bumbp versions for all subcharts * Remove kafka export as subchart Kafka exporter is useful for monitoring datahub, but it's not part of it. It should be deploy sepratly, as we do in production * Add script to bump versions together * Add tagging to the workflow * Don't run release on CI commits
* Release v0.9.1 Helm * Bump chart versions * Fixing final 210
* Bumping to release Helm charts for v0.9.2 * bump version by running: ./.github/scripts/bump-chart-versions.sh 0.2.112 Co-authored-by: szalai1 <szalaipeti.vagyok@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
JIRA issue link: https://sendbird.atlassian.net/browse/DATA-6011