Kubernetes 101章节-ngxin无法访问
Jiahe-J opened this issue · comments
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-app 1/1 Running 0 18m
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-app 1/1 Running 0 18m
$ kubectl describe pod nginx-app
Name: nginx-app
Namespace: default
Priority: 0
Node: docker-desktop/192.168.65.4
Start Time: Thu, 23 Dec 2021 11:05:28 +0800
Labels: run=nginx-app
Annotations:
Status: Running
IP: 10.1.0.12
IPs:
IP: 10.1.0.12
Containers:
nginx-app:
Container ID: docker://2b1079be0ea699dc151f178aa3d1c7aa5ce269424d2be0fa076e31d2f5f2a0dc
Image: nginx:alpine
Image ID: docker-pullable://nginx@sha256:12aa12ec4a8ca049537dd486044b966b0ba6cd8890c4c900ccb5e7e630e03df0
Port: 80/TCP
Host Port: 0/TCP
State: Running
Started: Thu, 23 Dec 2021 11:05:49 +0800
Ready: True
Restart Count: 0
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-qhv5j (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
kube-api-access-qhv5j:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: BestEffort
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 19m default-scheduler Successfully assigned default/nginx-app to docker-desktop
Normal Pulling 19m kubelet Pulling image "nginx:alpine"
Normal Pulled 18m kubelet Successfully pulled image "nginx:alpine" in 20.2142666s
Normal Created 18m kubelet Created container nginx-app
Normal Started 18m kubelet Started container nginx-app
$ curl http://10.1.0.12 无响应，是端口没暴露出来？
Pod IP 需要在集群内部才可以访问，外部访问需要Service
Pod IP 需要在集群内部才可以访问，外部访问需要Service
原来如此，还不清楚怎么进到集群内部做测试，Service可以的了，不过在yaml里面的"apiVersion"走了弯路。谢谢！