Skip to content

add deploy mode for klusterlet#114

Merged
openshift-merge-robot merged 1 commit intoopen-cluster-management-io:mainfrom
zhujian7:klusterlet-deploy-mode
Dec 15, 2021
Merged

add deploy mode for klusterlet#114
openshift-merge-robot merged 1 commit intoopen-cluster-management-io:mainfrom
zhujian7:klusterlet-deploy-mode

Conversation

@zhujian7
Copy link
Copy Markdown
Member

Signed-off-by: zhujian jiazhu@redhat.com

@zhujian7
Copy link
Copy Markdown
Member Author

/retest

@zhujian7 zhujian7 force-pushed the klusterlet-deploy-mode branch 2 times, most recently from 222876f to 0ed3309 Compare December 13, 2021 06:17
@zhujian7
Copy link
Copy Markdown
Member Author

zhujian7 commented Dec 13, 2021

Because of openshift/build-machinery-go#56, the verity failed.

@zhujian7 zhujian7 changed the title wip:add deploy mode for klusterlet add deploy mode for klusterlet Dec 13, 2021
Copy link
Copy Markdown
Member

@qiujian16 qiujian16 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/assign @zhiweiyin318 @xuezhaojun

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 13, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiujian16, zhujian7

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@zhujian7
Copy link
Copy Markdown
Member Author

cc @ianzhang366

@zhujian7 zhujian7 force-pushed the klusterlet-deploy-mode branch from 0ed3309 to 931fac6 Compare December 14, 2021 03:36
Signed-off-by: zhujian <jiazhu@redhat.com>
@zhujian7 zhujian7 force-pushed the klusterlet-deploy-mode branch from 931fac6 to a6878c0 Compare December 14, 2021 13:39
Comment thread operator/v1/types.go
// - In Detached mode, only crd and configurations are installed on one cluster(defined as hub-cluster). Controllers run in another cluster (defined as management-cluster) and connect to the hub with the kubeconfig in secret of "external-hub-kubeconfig"(a kubeconfig of hub-cluster with cluster-admin permission).
// For klusterlet:
// - In Default mode, all klusterlet related resources are deployed on the managed cluster.
// - In Detached mode, only crd and configurations are installed on the spoke/managed cluster. Controllers run in another cluster (defined as management-cluster) and connect to the mangaged cluster with the kubeconfig in secret of "external-managed-kubeconfig"(a kubeconfig of managed-cluster with cluster-admin permission).
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zhujian7 how do we specify the configuration of management-cluster to controllers?

Copy link
Copy Markdown
Member Author

@zhujian7 zhujian7 Dec 15, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact for registration-agent and work-agent, the configuration here specifically refers to the RBAC configuration(in the managed cluster). Currently, we don't need a configuration resource(cm, in the management cluster) for the controllers(registration-agent and work-agent), all configs are reflected by the flags.

@zhiweiyin318
Copy link
Copy Markdown
Member

/lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants