Skip to content
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

feat: add webook and external eps support dualstack #774

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

qiuwei68
Copy link
Contributor

@qiuwei68 qiuwei68 commented Dec 6, 2024

What type of PR is this?

/kind feature

What does this PR do?

add webook for virtualcluster cr and external eps support dualstack

Which issue(s) does this PR fix?

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


@qiuwei68 qiuwei68 force-pushed the feature_unittests branch 6 times, most recently from 8f5a5ae to 8c10923 Compare December 12, 2024 01:23
@duanmengkk
Copy link
Contributor

Unit test code should be submitted together with the logic code.

cmd/kubenest/operator/app/operator.go Show resolved Hide resolved
@@ -202,6 +209,7 @@ func startEndPointsControllers(mgr manager.Manager) error {
APIServerExternalSyncController := endpointscontroller.APIServerExternalSyncController{
Client: mgr.GetClient(),
EventRecorder: mgr.GetEventRecorderFor(constants.GlobalNodeControllerName),
KubeClient: kubeClient,
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a conflict between Client and KubeClient, and can they be reused?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Client is a client used for execution in the VC, while the KubeClient is a client used for execution in the host cluster. These two are used in different scenarios and do not conflict with each other

Namespace string
Name string
Vc *v1alpha1.VirtualCluster
RootClientSet kubernetes.Interface
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there no special necessity for the definition of this Resource struct, and does the name of the struct not reflect its purpose?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Since information from the Resource struct is needed, a struct is defined here and placed in the common package for use by multiple Go files. However, the struct name can be changed to better reflect its purpose.

@qiuwei68 qiuwei68 force-pushed the feature_unittests branch 3 times, most recently from 165dfc4 to 0fc2eb5 Compare December 18, 2024 01:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants