-
Notifications
You must be signed in to change notification settings - Fork 0
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
implementation of k8s client separation. #31
implementation of k8s client separation. #31
Conversation
…ate managers/clients to communicate with the service cluster (which holds the zalando postgresql resources) and the control plane cluster (which holds our fits postgres resources)
return ctrl.Result{}, err | ||
} | ||
log.Info("postgres status updated successfully", "status", newStatus) | ||
// Update status will be handled by the StatusReconciler, based on the Zalando Status |
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.
Needs discussion
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.
We don't need this part anymore.
@@ -90,12 +112,13 @@ func main() { | |||
}() | |||
|
|||
if err = (&controllers.PostgresReconciler{ | |||
Client: mgr.GetClient(), | |||
Client: ctrlPlaneClusterMgr.GetClient(), |
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.
How about an explicit name like ctrl
for the client of the control-plane cluster and another explicit name like svc
for the client of the service cluster?
Log: ctrl.Log.WithName("controllers").WithName("Status"), | ||
Scheme: mgr.GetScheme(), | ||
}).SetupWithManager(mgr); err != nil { | ||
Client: svcClusterMgr.GetClient(), |
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.
Like the above. How about an explicit name like svc
for the client of the service-cluster?
Separate k8s clients dev
…ervice_cluster_and_ctrl_cluster
We now use two separate managers/clients to communicate with the service cluster (which holds the zalando postgresql resources) and the control plane cluster (which holds our fits postgres resources).