-
Notifications
You must be signed in to change notification settings - Fork 561
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
Fixes for gc related tests #3999
Conversation
Hi @wyike. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -88,7 +88,7 @@ var _ = ginkgo.Describe("[managed] [gc] EKS Cluster external resource GC tests", | |||
cp := ms.GetControlPlaneByName(ctx, ms.GetControlPlaneByNameInput{ | |||
Getter: e2eCtx.Environment.BootstrapClusterProxy.GetClient(), | |||
Namespace: cluster.Spec.InfrastructureRef.Namespace, | |||
Name: cluster.Spec.InfrastructureRef.Name, | |||
Name: cluster.Spec.ControlPlaneRef.Name, |
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.
Control Plane Ref:
API Version: controlplane.cluster.x-k8s.io/v1beta2
Kind: AWSManagedControlPlane
Name: eks-extresgc-41ehz7-control-plane
Namespace: eks-extresgc-3lx403
Infrastructure Ref:
API Version: infrastructure.cluster.x-k8s.io/v1beta2
Kind: AWSManagedCluster
Name: eks-extresgc-41ehz7
Namespace: eks-extresgc-3lx403
Get the controlplane name from ControlPlaneRef
/ok-to-test |
@wyike - is there much more to do on this? |
Hi @richardcase, nothing more. Just have the question regarding to remove AUTO_CONTROLLER_IDENTITY_CREATOR. I am not sure if I should remove it, I am considering the removal because gc_managed case will fail as default identity cannot be automatically created, but I see this option is set as False because of AWSClusterStaticIdentity case support 7f14d22. If leaving it as the default value, the true , would it affect AWSClusterStaticIdentity related cases? Or AUTO_CONTROLLER_IDENTITY_CREATOR=true can also be compatible with these cases? What do you think? I read more on https://cluster-api-aws.sigs.k8s.io/topics/multitenancy.html and https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/docs/proposal/20200506-single-controller-multitenancy.md, it seems AUTO_CONTROLLER_IDENTITY_CREATOR=true won't affect AWSClusterStaticIdentity functionalities, right? |
Thats correct @wyike 👍 |
/test ? |
@richardcase: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test pull-cluster-api-provider-aws-e2e |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardcase The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #3998
Special notes for your reviewer:
Checklist: