-
Notifications
You must be signed in to change notification settings - Fork 38
fix: Simplify the flow of MC controller #220
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
Conversation
|
Clarification: So with this refactor all the resources like Namespace, role, role binding & Internal member cluster will exist until we delete the member cluster CR right ? |
|
Yes |
Arvindthiru
left a comment
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.
This needs to be removed
fleet/pkg/controllers/membercluster/membercluster_controller_integration_test.go
Lines 97 to 103 in a47a01d
| heartBeatReceivedCondition := metav1.Condition{ | |
| Type: fleetv1alpha1.ConditionTypeInternalMemberClusterHeartbeat, | |
| Status: metav1.ConditionTrue, | |
| Reason: "InternalMemberClusterHeartbeatReceived", | |
| ObservedGeneration: imc.GetGeneration(), | |
| } | |
| imc.SetConditions(joinedCondition, heartBeatReceivedCondition) |
But I can remove when I make changes to accommodate the heartbeat api
--------- Signed-off-by: Zhiying Lin <zhiyingl456@gmail.com>
Simplify the flow of MC controller. Will do manual testing later.
Here are the test results:
https://msazure.visualstudio.com/CloudNativeCompute/_wiki/wikis/CloudNativeCompute.wiki/355835/liqian-test-hub-agent