UPSTREAM: <carry>: OCPBUGS-90506: add secure metrics serving with TokenReview/SAR authentication - #200
Conversation
|
@Thealisyed: This pull request references Jira Issue OCPBUGS-90506, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
cb3ef99 to
84286dd
Compare
|
/jira refresh |
|
@Thealisyed: This pull request references Jira Issue OCPBUGS-90506, which is invalid:
Comment DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@Thealisyed: This pull request references Jira Issue OCPBUGS-90506, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
84286dd to
729bf5d
Compare
Expose ExternalDNS operand metrics to cluster Prometheus without using a kube-rbac-proxy sidecar. The operand now serves its own metrics over HTTPS with Kubernetes TokenReview/SAR auth via --metrics-tls-cert-dir (added in openshift/external-dns#200). - Add --metrics-tls-cert-dir arg and service-ca cert volume mount to each ExternalDNS container - Change --metrics-address from 127.0.0.1 to 0.0.0.0 so metrics are reachable outside the pod - Create a Service with serving-cert annotation for auto TLS - Create a ServiceMonitor for Prometheus discovery (HTTPS, port 7979+) - Add tokenreviews/subjectaccessreviews RBAC for the operand service account Depends on openshift/external-dns#200 for the operand-side auth layer. Assisted with Claude.
Expose ExternalDNS operand metrics to cluster Prometheus without using a kube-rbac-proxy sidecar. The operand now serves its own metrics over HTTPS with Kubernetes TokenReview/SAR auth via --metrics-tls-cert-dir (added in openshift/external-dns#200). - Add --metrics-tls-cert-dir arg and service-ca cert volume mount to each ExternalDNS container - Change --metrics-address from 127.0.0.1 to 0.0.0.0 so metrics are reachable outside the pod - Create a Service with serving-cert annotation for auto TLS - Create a ServiceMonitor for Prometheus discovery (HTTPS, port 7979+) - Add tokenreviews/subjectaccessreviews RBAC for the operand service account Depends on openshift/external-dns#200 for the operand-side auth layer. Assisted with Claude.
Expose ExternalDNS operand metrics to cluster Prometheus without using a kube-rbac-proxy sidecar. The operand now serves its own metrics over HTTPS with Kubernetes TokenReview/SAR auth via --metrics-tls-cert-dir (added in openshift/external-dns#200). - Add --metrics-tls-cert-dir arg and service-ca cert volume mount to each ExternalDNS container - Change --metrics-address from 127.0.0.1 to 0.0.0.0 so metrics are reachable outside the pod - Create a Service with serving-cert annotation for auto TLS - Create a ServiceMonitor for Prometheus discovery (HTTPS, port 7979+) - Add tokenreviews/subjectaccessreviews RBAC for the operand service account Depends on openshift/external-dns#200 for the operand-side auth layer. Assisted with Claude.
|
/assign |
alebedev87
left a comment
There was a problem hiding this comment.
The main approach LGTM, some remarks about minimizing the impact of the carrying the patch. Also, about the commit message and PR title - kube-rbac-proxy doesn't figure in external-dns context, it's something we add in the operator. Something like add secure metrics serving with TokenReview/SAR authentication would be more fitting into the context.
729bf5d to
8109021
Compare
…enReview/SAR authentication
8109021 to
9c589ae
Compare
|
@Thealisyed: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alebedev87 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@Thealisyed: Jira Issue OCPBUGS-90506: Some pull requests linked via external trackers have merged: The following pull request, linked via external tracker, has not merged: All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-90506 has not been moved to the MODIFIED state. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@Thealisyed: Jira Issue OCPBUGS-90506: Some pull requests linked via external trackers have merged: The following pull request, linked via external tracker, has not merged: All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-90506 has not been moved to the MODIFIED state. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Summary
--metrics-tls-cert-dirflag (directory containingtls.crtandtls.keyprovisioned by service-ca); defaults to empty string (plain HTTP) for backward compatibilitywithMetricsAuthusingk8s.io/client-godirectly — zero new dependenciesmetrics_openshift.go/metrics_openshift_test.goto minimise the carry patch diff inmain.go/healthzremains unauthenticated for kubelet liveness/readiness probesNote: