This repository has been archived by the owner on May 16, 2023. It is now read-only.
6.8.9 Release #616
Closed
6.8.9 Release #616
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
Member
jmlrt
commented
May 13, 2020
jmlrt
commented
- Remove beta notices and small doc updates
- Bump version to 6.8.9
We are starting using a git branching model like the Elastic Stack projects. This commit makes sure this `7.7` branch is using the 7.7.x-SNAPSHOT Docker images and this branch will be used for the development and release processes for the Helm Charts 7.7.x
[meta] fix ci jobs
The cluster names created for running tests can't contain the `.` character which is part of the branch name.
For doing the integration tests some GKE clusters are created. There is a dedicated job to cleanup these clusters at the end of the tests. This commit fixes the Jenkins configuration to make sure this upstream job (which does not need parameter) is triggered.
Metricbeat improvements
Filebeat improvements
This commit updates the remaining links to GitHub and Jenkins which had `master` as the branch name to 7.7
[helm] bump helm version to 2.16.6
* [script] Update bumper script to handle SNAPSHOT versions This commit updates the `bumper.py` script to handle the workflows for updating the versions to test staging artifacts and before a release, for example: - update 7.7.0-SNAPSHOT to 7.7.0 before tagging a release, by running `env BUMPER_VERSION_7="7.7.0" ./helpers/bumper.py` - update 7.7.0-SNAPHSHOT to 7.7.0-abcdefgh for testing staging artifacts by running: `env BUMPER_VERSION_7="7.7.0-abcdefgh" BUMPER_USE_STAGING_IMAGES="true" ./helpers/bumper.py` For now this script do not handle the bump from 7.7.0 to 7.7.1-SNAPSHOT for the next developement iteration after a release. In the meantime this update should be done manually.
…c#582) The multijob configuration for testing staging 7.7 artifacts was referencing jobs from another branch. This commit makes sure the configured jobs are all from the same git branch.
…ndom-key Use busybox for key generation in testing
[metricbeat] split values for daemonset and deployment
[metricbeat] add host networking option
[elasticsearch] Adds imagePullSecrets for test Pod
[elasticsearch] Set securityContext for test pod
Update defaults for extra values to support lists
[elasticsearch] update readiness probe endpoint
Added support for envFrom in apm-server, logstash, kibana and elasticsearch
[logstash] update doc and values.yaml for http.host issues
Doc improvements - Reformat all `README.md` files - Fix typos and missing syntaxes) - Use Markdown implicit link names - Sort values in configuration tables - Limit lines to 80 characters (except for code blocks and tables) - Add table of content - Fix default values descriptions - Move testing instructions to `CONTRIBUTING.md` doc - Move breaking changes notices to `BREAKING_CHANGES.md` doc
FAQ and examples improvements (elastic#598) - Add missing section in contributing guide - Add note about ECK - Add more FAQ topics - Document all examples - NIT: fixes typos...
This commit initiates the 6.8 branch which will be dedicated to the 6.8.x releases for the Helm Charts. It will allow to: - test this branch with the daily Stack Docker images 6.8.9-SNAPSHOT via dedicated Jenkins jobs - test the staging 6.8.x Docker images before a release This branch is based on [7.7](https://github.com/elastic/helm-charts/tree/7.7/) which was initiated in elastic#541. [Elasticsearch upgrade test](https://github.com/elastic/helm-charts/tree/7.7/elasticsearch/examples/upgrade) has been removed as doesn't make sense to try an upgrade from `7.0.0-alpha1` to `6.8.x`.
|
wrong target branch |
Merged
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.