The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Unable to connect to the server when using aws-eks-kubectl-run:2.2.0

Puja Agarwal
Puja Agarwal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
April 12, 2022

Hi,

I am using `aws-eks-kubectl-run:2.2.0` in bitbucket pipeline to deploy to AWS EKS cluster but facing the following issue:
 

Status: Downloaded newer image for bitbucketpipelines/aws-eks-kubectl-run:2.2.0
INFO: Configuring kubeconfig...
Added new context arn:aws:eks:ap-southeast-2:102468537709:cluster/eks-uat to /root/.kube/config
INFO: Successfully updated the kube config.
Unable to connect to the server: dial tcp 10.148.29.54:443: i/o timeout
✖ spec file validation failed.
Watch
Like Be the first to like this
2515 views

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Marcos Sampaio
Marcos Sampaio
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 12, 2022

Hi @Puja Agarwal ,

Since it is timing out, it could be a network connectivity issue.

  1. Does your cluster allow network access from this ip range?
  2. Is your EKS endpoint access public or private?
Reply
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security