-
Notifications
You must be signed in to change notification settings - Fork 366
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
Integrate the CRD puller into the cluster controller #20
Integrate the CRD puller into the cluster controller #20
Conversation
Signed-off-by: David Festal <dfestal@redhat.com>
Signed-off-by: David Festal <dfestal@redhat.com>
Signed-off-by: David Festal <dfestal@redhat.com>
Signed-off-by: David Festal <dfestal@redhat.com>
Signed-off-by: David Festal <dfestal@redhat.com>
Signed-off-by: David Festal <dfestal@redhat.com>
Signed-off-by: David Festal <dfestal@redhat.com>
cc @imjasonh |
@@ -142,7 +142,7 @@ func main() { | |||
"admin": {Cluster: "admin", AuthInfo: "loopback"}, | |||
"user": {Cluster: "user", AuthInfo: "loopback"}, | |||
} | |||
clientConfig.CurrentContext = "user" | |||
clientConfig.CurrentContext = "admin" |
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.
Does this mean we can remove the text about using this context?
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.
If you and @smarterclayton agree with this change here, then yes :-)
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.
So I assume that "silent is consent" @smarterclayton :-) and will merge the PR tomorrow if no more comment.
This PR integrates the CRD Puller into the cluster controller in order to pull some resources of a physical cluster (pods / deployment) inside the KCP and register them as CRDs when a physical cluster is joining.
Of course this is a very basic, minimal implementation, with no negociation at all in case of resource schema conflicts.
But this is sufficient to implement the case when adding a physical cluster brings back
pods
anddeployments
resources to the KCP.