opened
rmweir
username_0
<!--
Please search for existing issues first, then read https://rancher.com/docs/rancher/v2.x/en/contributing/#bugs-issues-or-questions to see what we expect in an issue
For security issues, please email security@rancher.com instead of posting a public issue in GitHub. You may (but are not required to) use the GPG key located on Keybase.
-->

**What kind of request is this (question/bug/enhancement/feature request):**
enhancement

**Steps to reproduce (least amount of steps as possible):**
1. Create or register private EKS cluster (a cluster that only has Private Access enabled).

**Result:**
Error: "Failed to communicate with cluster.
Even if a cluster is created as Public/Private then has public disabled, the agent will connect but health checks will error.

**Desire:**
Registering a private EKS cluster should work and rancher should be able to communicate with it.
Creating a private EKS cluster should work. This flow will still require the user to use a command to deploy the agent, similar to regular imported clusters, described here:  https://github.com/rancher/rancher/issues/28356.

**Notes:**
It is possible to import a private cluster through regular import. This is because imported clusters tunnel their kubernetes requests to the control plane node and communicate with the kubernetes service IP instead of the public endpoint. The solution for this should probably use this same approach for EKS clusters. Requests should be tunneled and instead of using the public Kube API endpoint, the kubernetes service ip should be used.

This is blocking: https://github.com/rancher/rancher/issues/28356
[EKSv2]: Rancher should be able to fully connect to created/register private EKS clusters
issue
closed
rmweir
username_0
issue