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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use elasticsearch operator 4.2, add workflow for 4.1 #631
Use elasticsearch operator 4.2, add workflow for 4.1 #631
Changes from 2 commits
a12ebcf
7a365f0
8cf4e74
df137d9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it run all e2e tests here, or just the es ones?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original OCP workflow run
es-self-provisioned
test group. This file is just copied to run the same CI as before.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jpkrohling Thoughts - should it just be limited to run the self provisioned tests? and also update the other workflow aswell?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@objectiser It seems like a separate issue/discussion. Could you please create an issue to discuss which tests should be run on OCP?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I think I would still like to know if something is broken when using an externally managed ES. It might have been limited first for development purposes, and I probably forgot to enable it for the other tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am might be missing something, but it seems to me we are talking about different things here.
There is a test for externally managed elasticsearch - the group name is
es
. The question is whether we want to run it on openshift, at the moment we run it only on k8s.I think externally managed elasticsearch test on openshift is not very important. However there might be other tests more suitable to run on Openshift e.g. test oauth proxy (I am not sure if there is such a test).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok will open a separate issue.