higress icon indicating copy to clipboard operation
higress copied to clipboard

安装higress探针检测connection refused

Open asd969704376 opened this issue 5 months ago • 5 comments

[root@master ~]# kubectl get pod --all-namespaces -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES higress-system higress-console-7f7c8496c-fc4zs 0/1 Running 4 (46s ago) 4m34s 10.244.2.113 node1 higress-system higress-controller-6dd78dd75f-cf654 0/2 Running 2 (33s ago) 4m34s 10.244.2.114 node1 higress-system higress-gateway-767884599d-5m5rr 0/1 ContainerCreating 0 4m34s 172.30.107.73 node1 higress-system higress-gateway-767884599d-8vg62 0/1 Pending 0 4m34s kube-flannel kube-flannel-ds-cdsq5 1/1 Running 0 21h 172.28.255.24 master kube-flannel kube-flannel-ds-kcq6f 1/1 Running 0 21h 172.30.107.73 node1 kube-system coredns-84df5b7799-8ps6r 1/1 Running 0 21h 10.244.0.7 master kube-system coredns-84df5b7799-t95ff 1/1 Running 0 21h 10.244.0.6 master kube-system etcd-master 1/1 Running 5 21h 172.28.255.24 master kube-system kube-apiserver-master 1/1 Running 5 21h 172.28.255.24 master kube-system kube-controller-manager-master 1/1 Running 1 21h 172.28.255.24 master kube-system kube-proxy-bdfz5 1/1 Running 0 21h 172.30.107.73 node1 kube-system kube-proxy-lb9p9 1/1 Running 0 21h 172.28.255.24 master kube-system kube-scheduler-master 1/1 Running 10 21h 172.28.255.24 master

[root@master ~]# kubectl describe pod -n higress-system higress-controller-6dd78dd75f-cf654 Name: higress-controller-6dd78dd75f-cf654 Namespace: higress-system Priority: 0 Service Account: higress-controller Node: node1/172.30.107.73 Start Time: Tue, 24 Sep 2024 11:36:53 +0800 Labels: app=higress-controller higress=higress-controller pod-template-hash=6dd78dd75f Annotations: Status: Running IP: 10.244.2.114 IPs: IP: 10.244.2.114 Controlled By: ReplicaSet/higress-controller-6dd78dd75f Containers: higress-core: Container ID: containerd://24b52d175b8eac256fd291dbd493cf771c0d8f53c09714c749dc7277a0457316 Image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/higress:1.4.2 Image ID: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/higress@sha256:fc9d1128fb6a13606e4b8ff4798b097e3a2cf573585f92ba0e869938397bb6b6 Ports: 8888/TCP, 8889/TCP, 15051/TCP Host Ports: 0/TCP, 0/TCP, 0/TCP Args: serve --gatewaySelectorKey=higress --gatewaySelectorValue=higress-system-higress-gateway --gatewayHttpPort=80 --gatewayHttpsPort=443 --ingressClass=higress --enableAutomaticHttps=true --automaticHttpsEmail= State: Running Started: Tue, 24 Sep 2024 11:41:06 +0800 Last State: Terminated Reason: Error Exit Code: 1 Started: Tue, 24 Sep 2024 11:38:54 +0800 Finished: Tue, 24 Sep 2024 11:40:54 +0800 Ready: False Restart Count: 2 Limits: cpu: 1 memory: 2Gi Requests: cpu: 500m memory: 2Gi Readiness: http-get http://:8888/ready delay=1s timeout=5s period=3s #success=1 #failure=3 Environment: POD_NAME: higress-controller-6dd78dd75f-cf654 (v1:metadata.name) POD_NAMESPACE: higress-system (v1:metadata.namespace) SERVICE_ACCOUNT: (v1:spec.serviceAccountName) DOMAIN_SUFFIX: cluster.local Mounts: /var/log from log (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-6xm88 (ro) discovery: Container ID: containerd://7540143771a5434e43f1ff78061519655bd267570e77d1aa0f774f8ee3dd3152 Image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/pilot:1.4.2 Image ID: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/pilot@sha256:5470f030bce6ed63770932b1807eb4d03c99628571efe82c14956da5cde01255 Ports: 8080/TCP, 15010/TCP, 15017/TCP Host Ports: 0/TCP, 0/TCP, 0/TCP Args: discovery --monitoringAddr=:15014 --log_output_level=default:info --domain cluster.local --keepaliveMaxServerConnectionAge 30m State: Running Started: Tue, 24 Sep 2024 11:36:54 +0800 Ready: False Restart Count: 0 Requests: cpu: 500m memory: 2Gi Readiness: http-get http://:8080/ready delay=1s timeout=5s period=3s #success=1 #failure=3 Environment: PILOT_ENABLE_HEADLESS_SERVICE_POD_LISTENERS: false HIGRESS_SYSTEM_NS: higress-system DEFAULT_UPSTREAM_CONCURRENCY_THRESHOLD: 10000 ISTIO_GPRC_MAXRECVMSGSIZE: 104857600 ENBALE_SCOPED_RDS: true ON_DEMAND_RDS: false HOST_RDS_MERGE_SUBSET: false PILOT_FILTER_GATEWAY_CLUSTER_CONFIG: true HIGRESS_CONTROLLER_SVC: 127.0.0.1 HIGRESS_CONTROLLER_PORT: 15051 REVISION: default JWT_POLICY: third-party-jwt PILOT_CERT_PROVIDER: istiod POD_NAME: higress-controller-6dd78dd75f-cf654 (v1:metadata.name) POD_NAMESPACE: higress-system (v1:metadata.namespace) SERVICE_ACCOUNT: (v1:spec.serviceAccountName) KUBECONFIG: /var/run/secrets/remote/config PRIORITIZED_LEADER_ELECTION: false INJECT_ENABLED: false PILOT_ENABLE_CROSS_CLUSTER_WORKLOAD_ENTRY: false PILOT_ENABLE_METADATA_EXCHANGE: false PILOT_SCOPE_GATEWAY_TO_NAMESPACE: false VALIDATION_ENABLED: false PILOT_TRACE_SAMPLING: 1 PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_OUTBOUND: true PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_INBOUND: true ISTIOD_ADDR: istiod.higress-system.svc:15012 PILOT_ENABLE_ANALYSIS: false CLUSTER_ID: Kubernetes CUSTOM_CA_CERT_NAME: higress-ca-root-cert Mounts: /etc/cacerts from cacerts (ro) /etc/istio/config from config (rw) /var/run/secrets/istio-dns from local-certs (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-6xm88 (ro) /var/run/secrets/remote from istio-kubeconfig (ro) /var/run/secrets/tokens from istio-token (ro) Conditions: Type Status PodReadyToStartContainers True Initialized True Ready False ContainersReady False PodScheduled True Volumes: log: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium:
SizeLimit: config: Type: ConfigMap (a volume populated by a ConfigMap) Name: higress-config Optional: false local-certs: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: Memory SizeLimit: istio-token: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 43200 cacerts: Type: Secret (a volume populated by a Secret) SecretName: cacerts Optional: true istio-kubeconfig: Type: Secret (a volume populated by a Secret) SecretName: istio-kubeconfig Optional: true kube-api-access-6xm88: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: Burstable Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message


Normal Scheduled 6m3s default-scheduler Successfully assigned higress-system/higress-controller-6dd78dd75f-cf654 to node1 Normal Pulled 6m2s kubelet Container image "higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/higress:1.4.2" already present on machine Normal Created 6m2s kubelet Created container higress-core Normal Started 6m2s kubelet Started container higress-core Normal Pulled 6m2s kubelet Container image "higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/pilot:1.4.2" already present on machine Normal Created 6m2s kubelet Created container discovery Normal Started 6m2s kubelet Started container discovery Warning Unhealthy 5m42s (x10 over 6m1s) kubelet Readiness probe failed: Get "http://10.244.2.114:8888/ready": dial tcp 10.244.2.114:8888: connect: connection refused Warning Unhealthy 60s (x113 over 6m1s) kubelet Readiness probe failed: Get "http://10.244.2.114:8080/ready": dial tcp 10.244.2.114:8080: connect: connection refused

请问下这是什么原因 是我的k8s搭建的有问题吗

asd969704376 avatar Sep 24 '24 03:09 asd969704376