[Sync] Sync with remote #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: Add support for modifying edge probe values This allows BASE_PATH enviornment variable changes to be reflected in the values.yaml file. Without this, k8s will attempt to hit /internal-backstage/health, while the helm-edge application is reporting health values at /BASE_PATH/internal-backstage/health. * Bump chart minor version * Set up defaults for unleash-edge nodes
* chore: Added liveness and readiness probe to CI values file * Bumped default app version for unleash and edge
…#101) * feat: Bump Edge to 16.0.1, and default to json for logformat * chore(ci): Bump chart-testing-action
* feat: release 2.1.0 of Edge chart * use 2.6.0 of chart-testing * fix: removed timeout flag
…lm chart more configurable for more secure environments (Unleash#111) Co-authored-by: yuvals41 <[email protected]>
--------- Co-authored-by: Gastón Fournier <[email protected]>
Support for pod labels
allow ssl configuration
…sh#110) Update `test-connection.yaml` in the Unleash proxy Helm chart to use an authenticated route. The /proxy/health route of the Unleash proxy does not require authentication. The Authentication header is ignored for this route. Even if there's an issue with the way client shared secrets are configured, the test-connection.yaml test will succeed. Using the /proxy route (which does require authentication) allows testing a shared secret. This change implements the recommended method to test the proxy deployment from https://docs.getunleash.io/how-to/how-to-run-the-unleash-proxy#verify-that-the-proxy-is-working Also update the way `wget` is called (the Authentication header was not correctly set, but as it was ignored this mistake was not visible). Note: The same Helm value is used to configure the proxy shared secrets environment variable, and the authentication header in test-connection.yaml. As such, as long as the chart is correct, the user can't actually make a mistake here. However, this test is misleading to a user reading the chart templates and manually reproducing the test against the deployed proxy, as the current test does not actually validates shared secrets. * chore: bump chart version to 0.6.3
…nleash#122) * bug: don't set default "requests" in Unleash Edge chart values.yaml setting up default "requests" makes it impossible to omit certain portions of "requests" in local values.yaml file, e.g. not setting resources.limits.cpu is impossible * updated unleash-edge chart version to reflect default requests removal --------- Co-authored-by: m-barczyk <[email protected]>
…ight have the wrong path (Unleash#123)
* feat: generic extra manifests for unleash chart This allows including resources like credentials for the database connection or the secret env vars for unleash (e.g. shared secret, google client secret, ...) from a 3rd-party secrets provider and then referencing those secrets in the "existing secrets"
* fix: Secrets fullname and add CI test for secrets * fix: Release workflow badge URL
* chore: update unleash to 5.8.1 * chore: update version number
* chore: bump edge version to v17.1.0 * style: fix quote formatting
…h#135) * feat(unleash): db - username and password, not url to connect Handling special characters in postgres database urls can be challenging. Using username and password directly is easier. I have tested this with the password 'unl:e@sh:444'
- Unleash looks for DATABASE_NAME, it does not look for DATABASE, so this has actually not been working earlier fixes: Unleash#136
* feat: added configurable DATABASE_SSL_* possibilities * Update sslFiles.yaml * Bump app version to 5.12 with added support for specific database ssl
…sh#148) * chore: update with link to community doc
* chore: update action versions
* chore: upgrade unleash version
Unleash should work well if example resources are being used, so lets bump them so they can handle some data and traffic.
* add pod labels in deployment resource * bump chart version for new functionality
…ash#154) * fix: Include name helper for container name in all three charts fixes: Unleash#153 * use correct template name in edge * added document marker to top of deployment files
* task: updates versions of edge and unleash * Turn off false positive checks * Kind has not released newest tags yet
* fix templating * fix template and bump chart version
Co-authored-by: Patrick Vickery <[email protected]>
pqn
approved these changes
Jul 30, 2024
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.
Sync with Unleash@68731b8