-
Notifications
You must be signed in to change notification settings - Fork 4
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
⚠️ Deprecate metrics-bind-addr flag #70
Conversation
Upgrading controller-runtime to v0.17.2 resolves the linting issues. |
# Conflicts: # go.mod # go.sum
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.
- Don't forget updating the kustomize manifests:
--metrics-bind-address
is still in use there. And I'd really also go with--insecure-diagnostics
for now. - However, we should at least provide the RBAC required for secure diagnostics:
// Add RBAC for the authorized diagnostics endpoint.
// +kubebuilder:rbac:groups=authentication.k8s.io,resources=tokenreviews,verbs=create
// +kubebuilder:rbac:groups=authorization.k8s.io,resources=subjectaccessreviews,verbs=create
Seems like #70 (review) was forgotten? |
I did not, just forgot to push ;) |
So, maybe you wanna push now? |
Have you tested the secured metrics port? So were you able to retrieve metrics after creating a role + binding and querying the port as the one the role was bound to? |
Yes, I did. I tried exactly what was described in Cluster API documentation |
Quality Gate passedIssues Measures |
What is the purpose of this pull request/Why do we need it?
See: https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.5-to-v1.6
See: kubernetes-sigs/cluster-api#9264
Checklist: