-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Make it possible to enable Prometheus metrics for Cilium #8433
Conversation
Hi @olemarkus. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
5da1d4e
to
6836ec1
Compare
@rifelpet anything holding this one back? |
/retest |
/test pull-kops-e2e-kubernetes-aws |
k8s/crds/kops.k8s.io_clusters.yaml
Outdated
@@ -2666,8 +2666,6 @@ spec: | |||
type: boolean | |||
prefilterDevice: | |||
type: string | |||
prometheusServeAddr: | |||
type: string |
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.
Do we allow removals like this?
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.
That is indeed the question. At some point we do because it is just confusing for end users if we leave it in. And no one can be using that since it doesn't do anything.
If we have a more clear deprecation guide, I can do the removal in a second PR.
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.
My understanding is that we need to leave them in unused. When we create a new API version, then we can remove it from the new version. My understanding might be inaccurate and I don't know how we're tracking items to change in the next API revision.
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 removed this bit now. Can be fixed at a later time, I guess
6836ec1
to
eed15b4
Compare
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus, rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
And yes we should open a GH issue that tracks any breaking changes we want to make across the entire kops API like removing the unused |
/retest |
…3-origin-release-1.15 Automated cherry pick of #8433: Make it possible to enable Prometheus metrics for Cilium
…3-origin-release-1.16 Automated cherry pick of #8433: Make it possible to enable Prometheus metrics for Cilium
…3-origin-release-1.17 Automated cherry pick of #8433: Make it possible to enable Prometheus metrics for Cilium
Another bug in the new templates is the loss of prometheus metrics.
Since there are more cilium components involved here, the old config param didn't make that much sense anymore, so I rewrote that part.
Since the property is removed, this sort of breaks BC, but nothing would have happened for those that did so no loss of functionality.
/kind bug