This repository has been archived by the owner on May 16, 2023. It is now read-only.
[kibana] update the upgrade test #1695
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
jmlrt
force-pushed
the
kibana-upgrade
branch
from
ad825a6
to
ddb7a82
Compare
|
Kibana upgrade test is fixed. This is ready for review. |
framsouza
approved these changes
Sep 13, 2022
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.
Fix the kibana upgrade test by installing Elasticsearch and Kibana 7.17.1 first, before upgrading them to 8.4.1 (because Kibana 7.17.1 can't connect to Elasticsearch 8.4.1).
Also fix the post-delete hook that was deleting kibana token during the upgrade, making impossible for the new kibana pod to connect to Elasticsearch.