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
Add ServiceMonitor CRD to cluster essentials #2429
Add ServiceMonitor CRD to cluster essentials #2429
Conversation
@@ -16,8 +16,6 @@ spec: | |||
namespace: "istio-system" # KNative comes with namespaces hardcoded so this one is only for installer | |||
- name: "istio-kyma-patch" | |||
namespace: "istio-system" | |||
- name: "prometheus-operator" |
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.
Contact @klaudiagrz and extend documentation about how to enable monitoring,
/test pre-master-kyma-gke-integration |
I don't like that prometheus-operator stays a separate module, should be merged with monitoring module. After talking to @joek it seems to not be a trivial taks to merge them, I will create a follow-up for that. |
Co-Authored-By: derberg <derberg@wp.pl>
@derberg: The following tests failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Description
This would be a temporary solution to enable local development without heavy Prometheus. Long term I will work with @PK85 on proposal how to do modularization the same way in all charts instead of solving modularization challenges case by case.
Changes proposed in this pull request:
Kyma resource consumption on minikube without Prometheus:
Related issue(s)
Resolves #1840