-
Notifications
You must be signed in to change notification settings - Fork 107
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
Disable kube-rbac-proxy by default #50
Conversation
HNC does not expose PII information via `/metrics` endpoint. Disabling employing kube-rbac-proxy by default.
Welcome @vishh! |
Hi @vishh. Thanks for your PR. I'm waiting for a kubernetes-sigs 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 Hey Ryan, the kube-rbac-proxy has been causing us some trouble, e.g. staying on top of the latest version internally at Google for Hierarchy Controller, and also figuring out which multiarch version to use for #45. @vishh (who's a Googler starting to work on HNC) reviewed the metrics and we don't think there's any reason to protect them with the RBAC proxy as it's all pretty innocuous. wdyt? @vishh, did you deploy this to one of your own clusters and run any e2e tests (e.g. |
I can run e2e tests, but I felt a kustomize build was sufficient for this
change.
…On Thu, Jun 24, 2021 at 12:34 PM Adrian Ludwin ***@***.***> wrote:
/ok-to-test
/cc @rjbez17 <https://github.com/rjbez17>
Hey Ryan, the kube-rbac-proxy has been causing us some trouble, e.g.
staying on top of the latest version internally at Google for Hierarchy
Controller, and also figuring out which multiarch version to use for #45
<#45>.
@vishh <https://github.com/vishh> (who's a Googler starting to work on
HNC) reviewed the metrics and we don't think there's any reason to protect
them with the RBAC proxy as it's all pretty innocuous. wdyt?
@vishh <https://github.com/vishh>, did you deploy this to one of your own
clusters and run any e2e tests (e.g. make test-smoke)? If so, can you
please add a "Tested:" comment to your commit (example
<89b6f66>)?
Note that the Prow presubmits don't run e2e tests, only the postsubmits.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV4QKCMFZNFNSID6PEUTF3TUOCE3ANCNFSM47IQAJVQ>
.
|
@adrianludwin ran smoke tests and they passed against my GKE cluster. |
Cool, thanks. Ryan, lgty? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianludwin, rjbez17, vishh 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 |
HNC does not expose PII information via
/metrics
endpoint. Disabling employing kube-rbac-proxy by default.Tested: make test-smoke passes.