Accessing Private EKS Cluster from CodePipeline within the Same VPC #31440
Unanswered
qcserestipy
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Context
I have a setup where:
eks.Cluster.from_cluster_attributes
method. This pipeline is responsible for deploying application resources such as Helm charts and Kubernetes manifests.Both pipelines are within the same AWS account and region. The VPC configuration and the networking setup in both pipelines ensure that the
CodeBuild
steps are run within the same VPC as the EKS cluster.Problem
public_and_private
, everything works as expected, and the resources are successfully deployed to the cluster from Pipeline B.private
, the connection from the kubectl lambda function in Pipeline B to the EKS cluster times out.What I’ve Tried
Expected Behavior
The kubectl lambda in Pipeline B should be able to access the private EKS cluster endpoint without timing out when the cluster is configured as private. This should allow the pipeline to deploy resources (Helm charts, Kubernetes manifests) without the need for a public endpoint.
Actual Behavior
The kubectl lambda is unable to reach the private EKS cluster endpoint, resulting in a timeout during Kubernetes-related operations (such as Helm installations or
kubectl
commands).Request for Assistance
Code Snippets
Cluster Import Stack in Pipeline B
Relevant Pipeline B
Cluster Creation Stack in Pipeline A
Beta Was this translation helpful? Give feedback.
All reactions