Open sebltm opened 1 month ago
This issue is currently awaiting triage.
If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/kind bug
What steps did you take and what happened: The AWSManagedControlPlane has a field for setting the control plane endpoint. However, if that field is set when the CR is deployed, it gets overridden with the AWS-provided EKS endpoint once the EKS control plane comes up. This endpoint is then used when creating the kubeconfig.
What did you expect to happen: If the
controlPlaneEndpoint
is set when the CR is deployed, it should not be overridden after the EKS control plane becomes available.Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] In our case, we are creating the EKS control plane on an isolated subnet which is not reachable outside of the VPC and our management cluster is not hosted in AWS. We are then exposing the EKS control plane using an NLB on a different subnet which is reachable from outside the VPC and which is pointed to by a record that we create and is not known to AWS. This is how we would like to reach the cluster.
Environment:
kubectl version
):/etc/os-release
):