[OSSM-8154] Remove Custom Prometheus operator and test #744
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
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.
After the community Prometheus operator is deleted (which I added last week by #739 ), there is an issue in some monitoring-related Prometheus/alertmanager pods in openshift-monitoring namespace. The cluster already contains the Prometheus operator for openshift-monitoring so probably there is some incompatibility between in cluster Prometheus operator vs community one ( which is two years old btw :/ ) [probably the Prometheus community operator does something during the uninstalling which badly influences in cluster Prometheus operator]. So this pr removes it from MTT.
However, Incluster Prometheus operator doesn't manage Prometheus CR in custom namespaces so right now, there is no way to install custom Prometheus via Prometheus CR or install Prometheus operator via OLM anymore. ( In that case, I suggest to remove custom prometheus test from MTT [since we have a test for integration with openshift monitoring prometheus instance and it test the same things]
https://master-jenkins-csb-servicemesh.apps.ocp-c1.prod.psi.redhat.com/job/maistra/job/maistra-test-tool/2777/