search

aws-quickstart / quickstart-qingcloud-kubesphere

AWS Quick Start Team
Apache License 2.0
8 stars 7 forks source link

can't access console web from external-ip after installed #89

Open lanlin opened 2 years ago

lanlin commented 2 years ago

CloudFormation Status

image

My Options (region: cn-north-1)

Key Value Parsed Value
Alerting false -
Auditing true -
AvailabilityZones cn-north-1a,cn-north-1b -
Devops true -
EKSClusterName kubesphere -
Events false -
KeyPairName xxx -
Kubeedge true -
Logging true -
MetricsServer true -
Multicluster none -
Networkpolicy true -
NodeInstanceType t3.xlarge -
NumberOfAZs 2 -
NumberOfNodes 2 -
Openpitrix true -
PerAccountSharedResources AutoDetect -
PerRegionSharedResources AutoDetect -
PrivateSubnet1CIDR 10.0.0.0/19 -
PrivateSubnet2CIDR 10.0.32.0/19 -
PrivateSubnet3CIDR 10.0.64.0/19 -
ProvisionBastionHost Enabled -
PublicSubnet1CIDR 10.0.128.0/20 -
PublicSubnet2CIDR 10.0.144.0/20 -
PublicSubnet3CIDR 10.0.160.0/20 -
QSS3BucketName aws-quickstart -
QSS3BucketRegion us-east-1 -
QSS3KeyPrefix quickstart-qingcloud-kubesphere/ -
RemoteAccessCIDR 0.0.0.0/0 -
Servicemesh true -
VPCCIDR 10.0.0.0/16 -

Verification

kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f

......
Start installing events
Start installing kubeedge
Start installing logging
Start installing servicemesh
**************************************************
Waiting for all tasks to be completed ...
task alerting status is successful  (1/11)
task network status is successful  (2/11)
task logging status is successful  (3/11)
task kubeedge status is successful  (4/11)
task auditing status is successful  (5/11)
task multicluster status is successful  (6/11)
task events status is successful  (7/11)
task servicemesh status is successful  (8/11)
task devops status is successful  (9/11)
task openpitrix status is successful  (10/11)
task monitoring status is successful  (11/11)
**************************************************
Collecting installation results ...
#####################################################
###              Welcome to KubeSphere!           ###
#####################################################

Console: http://10.0.36.62:30880
.....

then I access the external-ip address: xxxxxxx-xxxxxx.cn-north-1.elb.amazonaws.com.cn, the AWS load balancer forward 80 to 30880. the access timeout after a long time wait.

even I try to access it from inside EKSBastion EC2 (curl -v http://10.0.36.62:30880), it still shows a timeout

lanlin commented 2 years ago

I have tried rebuilding several times in the region of "cn-north-1", but it still not working. But it works in the region of "ap-northeast-1".

FeynmanZhou commented 2 years ago

Hi @lanlin ,

We are trying to reproduce this issue in "cn-north-1". Could you please provide your environment for us to troubleshoot it?

lanlin commented 2 years ago

@FeynmanZhou what should I do?

FeynmanZhou commented 2 years ago

@lanlin We will contact you via email.

FeynmanZhou commented 2 years ago

@lanlin We will contact you via email.

@lanlin Have you received our email?

lanlin commented 2 years ago

@FeynmanZhou We are very sorry, but we are not allowed to provide test accounts