I have established a Kops Kubernetes cluster in AWS China, utilizing EC2 instances within the AWS China region and leveraging AWS China services such as subnets, VPC, and an internet gateway. The security group rules have been configured to allow all traffic.
However, when executing kops export kubeconfig, the configuration is imported successfully. Nevertheless, upon running kubectl get nodes, an issue arises indicating an inability to access and a "no such host" error. I have already made modifications to the DNS records for the public hosted zone, incorporating the private IP of the main node instance. Despite these efforts and the inclusion of an internet gateway, the issue persists.
Additionally, during an SSH session to the master -node instance, attempts to ping Google were unsuccessful. I have also created a test instance within the same VPC, equipped with a public IP and an internet gateway; however, it still cannot establish a connection to the internet. Efforts to modify the Route 53 main-nodes record by adding the private IP of the main-nodes instance have not yielded a resolution.
I am seeking guidance on identifying the root cause of these connectivity issues and effective solutions to address them. Any insights or recommendations to resolve these challenges would be greatly appreciated.
AWS OFFICIALUpdated a year ago
