-
Notifications
You must be signed in to change notification settings - Fork 3.4k
fix(CFP & Enhancement): remove service monitor enable values #36013
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
Conversation
5125d46
to
e891688
Compare
Thanks! While I understand the use-case, this will now create a service for users who are using metrics, but don't care about service monitor, but also don't want or need services. Would it make sense to instead introduce a new variable |
Thanks for the review. I also think it makes sense to introduce a new variable to help some users who want more control over service creation. Can I try it now? |
e891688
to
2b9138a
Compare
Sure, you are more than welcome to give it a shot. Since I see you are a first time contributor, please note the following when adding new Helm values:
Thanks! |
2b9138a
to
d97c064
Compare
@saiaunghlyanhtet I see you pushed to the branch, but no changes adding the values seem to have been made? |
Commit 5330e84 does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
Commits 5330e84, 5a382bc do not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
@gandro I am sorry. I forgot and synced my forked repo via GitHub. Now, I have merge commits that are not signed off. But I made the changes in my latest commit. |
@gandro Can you review the latest changes? Because of unsigned merge commits, do I need to create a new pull request so that history can be clear? |
I think we should set the You should be able to clean up the git history via |
4844077
to
0cef80d
Compare
@gandro I made changes as requested. Can you check it again, please? |
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.
Thanks, seems like the rebase worked. There are still some inconsistencies in the value use that I didn't spot before
install/kubernetes/cilium/templates/cilium-operator/service.yaml
Outdated
Show resolved
Hide resolved
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.
Starting to look good. One issue still and once done please squash all your commits into one (e.g. with git rebase -i main
)
03099c0
to
d5852dc
Compare
d5852dc
to
0b2c4bf
Compare
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.
Thank you!
/test |
CI is red because of an unrelated issue: #36100 I'll rebase and restart CI |
/test |
162f716
to
1d6426a
Compare
Signed-off-by: saiaunghlyanhtet <saiaunghlyanhtet2003@gmail.com>
1d6426a
to
ca71750
Compare
/test |
@saiaunghlyanhtet Just a heads-up, there is no need to rebase unless there are issues with CI. In fact, rebasing invalidates the last CI run, so we will have to re-run CI again after each rebase. |
There are at least 6 |
Title: Decouple Metrics Service Creation from ServiceMonitor in Cilium Helm Chart
Description: This pull request addresses the issue where the creation of metrics services for cilium-agent and cilium-operator is tied to the creation of ServiceMonitors in the Cilium Helm chart. Currently, enabling Prometheus with the default Helm values results in both the creation of metrics services and ServiceMonitors. This tight coupling prevents use cases where only metrics services are required without the ServiceMonitor.
Changes:
Updated the Cilium Helm chart templates for cilium-agent and cilium-operator to decouple the creation of metrics services from the creation of ServiceMonitors.
Modified the condition that checks for the prometheus.serviceMonitor.enabled flag, ensuring the creation of metrics services is independent of ServiceMonitor creation.
Motivation:
Users may want to deploy the metrics service without relying on ServiceMonitors, especially in environments where a custom Prometheus setup is used or where ServiceMonitors are not needed.
The change allows for more flexible Prometheus integration without forcing the creation of ServiceMonitors.
Fixes: #34466