Bump db-operator appVersion to 2.0.0 #16
Closed
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
* Migrate project to the `db-operator` org * Trigger action * Bump charts versions * Update the domain * Update the app version on db-operator chart * chore: Update the cloudish-sql version * refactor: Update api names * fix: Update db-auth-gateway images * fix: Update db-auth-gateway images in Readme.md
* chore: Update chart and app versions * feat(db-operator): Add `template` to postgres object
* Format the test worflow * Test against more k8s versions * Upgrade the chart version * Drop support for 1.21 * Add a `prerelease` label to k8s version
* Add an ability to set labels to DbInstances * Upgrade the db-instances chart to 1.4.2
* Make the webhook creation optional Not everybody needs a webhook, so it makes sense to make its creation optional. Also, I've added a very basic test for values, that is checking if the wished files are generated by helm using certain values files. I'd say it's rather a temporary solution, but currently, I don't know a better option Issue: db-operator/db-operator#38 * build: Upgrade k8s versions in tests New versions of Kubernetes were released. I've updated them to have ones that are currently actual in the CI pipeline
* Uprade db-operator to 1.13.0 version I've upgraded db-operator to 1.13.0 and added new CRD to templates. Also, I've added support for --check-for-changes arg * Update old CRDs to controller-get 0.12.0 * Replace "kci" with "kinda" in CRDs files names * Upgrade db-operator to 1.13.1
Name and namespace were hardcoded and so the the webhook servcice couldn't be reached when one tries to apply dbuser manifests
* docs: How to upgrade db-operator to 1.11.0 * build: Don't run linter if charts were not changed
* Remove the CHANGELOG from repo * Upgrade db-operator version to 1.15.3
* Update db-operator to 1.16.0 * Update db-operator to 1.16.1
* Setup pg_exporter queris with toYaml When it's configured with a multi-line string it's not possible to remove or replace a part of configuration * Create a ServiceMonitor per DbInstance I've added tests so we can check the pg_exporter is really having the data scraped by the prometheus operator using the ServiceMonitor * Post-review edit and rename files to snake case * Post-review minor fixes * Fix the test a bit
* Enable the AUTO_DISCOVERY on the pg_exporter * Fix the env var that should be text * Make the autodiscovery optional
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.
No description provided.