Closed Xunzhuo closed 1 month ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Xunzhuo Once this PR has been reviewed and has the lgtm label, please assign jeremyot for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
I think this should probably be used at https://github.com/kubernetes-sigs/mcs-api/blob/2833f83cfbdc46d80e0e18111ec977c4ef16e51d/conformance/connectivity_test.go#L92-L93 instead of creating a new ServiceExport inline there.
I think this should probably be used at
instead of creating a new ServiceExport inline there.
I think statically defining the resource objects is fine for the two simple tests we have now. But as we expand the tests, we'll likely want to create more than one service and headless services and maybe alter the service spec. So I think defining them globally/statically becomes less useful and maybe cumbersome. I think it's more useful to have functions to create them, eg createServiceExport(name string)
(which I've added locally in a pending commit).
This PR can be closed in favor of https://github.com/kubernetes-sigs/mcs-api/pull/60 which is a duplicate but it is newer and active.
Thanks @Xunzhuo for your contribution; I’ve merged #60 which is more comprehensive.
/close
@skitt: Closed this PR.
PR needs rebase.
helloServiceExport is not used in anywhere