-
Notifications
You must be signed in to change notification settings - Fork 14
WIP: Turn clusterName:string into a type parameter #2
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Dr. Stefan Schimanski <stefan.schimanski@gmail.com>
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.
Im just observing for now, but anything is better than string
:)
// and managing the lifecycle of each cluster, calling `Engage` on the manager | ||
// it is run against whenever a new cluster is discovered and cancelling the | ||
// context used on engage when a cluster is unregistered. | ||
// | ||
// Example: A Cluster API provider would be responsible for discovering and | ||
// managing clusters that are backed by Cluster API resources, which can live | ||
// in multiple namespaces in a single management cluster. | ||
type Provider interface { | ||
type TypedProvider[cluster comparable] interface { |
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.
Nit: Should this generic maybe be called something else, since cluster
seems confusing? Something like clusterIdentifier
?
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
PR needs rebase. 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-sigs/prow repository. |
No description provided.