AWS announces AWS Interconnect – multicloud (preview), providing simple, resilient, high-speed private connections to other cloud service providers. AWS Interconnect - multicloud is easy to configure and provides high-speed, resilient connectivity with dedicated bandwidth, enabling customers to interconnect AWS networking services such as AWS Transit Gateway, AWS Cloud WAN, and Amazon VPC to other cloud service providers with ease.
Rancher - Unable to import clusters
I have installed rancher with helm chart approach on EKS cluster using this link. https://rancher.com/docs/rancher/v2.6/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart with Rancher Generated TLS Certificate and manually had to edit Ingress to add IngressClass:nginx. As a pre-req, I also deployed ingress controller using Step 5, https://rancher.com/docs/rancher/v2.6/en/installation/resources/k8s-tutorials/amazon-eks/. I did not setup route53 , but using LoadBalancer Domain as is to login to rancher. Am able to login rancher, but unable to create/import existing clusters. Goes into provision mode and on Condition tabs shows "But get message <[Disconnected] Cluster agent is not connected", "Waiting For API to be available", " [Error] Error while applying agent YAML, it will be retried automatically: exit status 1, Unable to connect to the server: remote error: tls: internal error"
- Topics
- Containers
- Language
- English
- Newest
- Most votes
- Most comments
Hello, besides checking the usual IAM roles, I would suggest you make sure the ingress configuration and load balancer are set up correctly to expose Rancher. Issues here could prevent the Rancher agent from connecting.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 6 months ago
