参考文档：

Basic operations

kubernetes如何访问pod服务

k8s 如何对外提供服务

Kubernetes dashboard 通过 Ingress 提供HTTPS访问

接上文：ubuntu20.04下使用juju+maas环境部署k8s-8-基本操作-1-访问 kubernetes dashboard

k8s 向外提供服务有几种办法：
1 port-foward
2 node-port
3 ingress

port-forward方法：

例如，有个pod 叫做microbot-75cfc77b98-58rqh ，它通过80端口对外提供服务，那么我就可以使用kubectl port-forward pod/microbot-75cfc77b98-58rqh 8080:80将其映射到本机的8080端口上。你可以使用kubectl port-forward -h查看更多用法。

查看服务：

kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
kubernetes   ClusterIP   10.152.183.1     <none>        443/TCP          34d
microbot     ClusterIP   10.152.183.8     <none>        80/TCP           2d1h
web          NodePort    10.152.183.239   <none>        8080:31961/TCP   23d

查看pod

 kubectl get pod
NAME                        READY   STATUS    RESTARTS   AGE
microbot-75cfc77b98-58rqh   1/1     Running   0          2d1h
microbot-75cfc77b98-h2ttn   1/1     Running   0          2d1h
microbot-75cfc77b98-zt5rx   1/1     Running   0          2d1h

端口映射：

 kubectl port-forward pod/microbot-75cfc77b98-58rqh 8080:80 &

查看链接：

 curl http://localhost:8080
Handling connection for 8080
<!DOCTYPE html>
<html>
  <style type="text/css">
    .centered
      {
      text-align:center;
      margin-top:0px;
      margin-bottom:0px;
      padding:0px;
      }
  </style>
  <body>
    <p class="centered"><img src="microbot.png" alt="microbot"/></p>
    <p class="centered">Container hostname: microbot-75cfc77b98-58rqh</p>
  </body>
</html>

Ingress方法：

查看服务：

kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
kubernetes   ClusterIP   10.152.183.1     <none>        443/TCP          33d
microbot     ClusterIP   10.152.183.8     <none>        80/TCP           22h
web          NodePort    10.152.183.239   <none>        8080:31961/TCP   21d

查看服务microbot：

kubectl get svc microbot -o wide
NAME       TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE   SELECTOR
microbot   ClusterIP   10.152.183.8   <none>        80/TCP    22h   app=microbot

查看详细的microbot服务内容：

 kubectl describe svc microbot
Name:              microbot
Namespace:         default
Labels:            app=microbot
Annotations:       <none>
Selector:          app=microbot
Type:              ClusterIP
IP Family Policy:  SingleStack
IP Families:       IPv4
IP:                10.152.183.8
IPs:               10.152.183.8
Port:              <unset>  80/TCP
TargetPort:        80/TCP
Endpoints:         10.1.50.8:80,10.1.89.10:80,10.1.89.9:80
Session Affinity:  None
Events:            <none>

在kubernetes-dashboard中查看ingress的配置：



kind: Ingress
apiVersion: networking.k8s.io/v1beta1
metadata:
  name: microbot-ingress
  namespace: default
  uid: e8d52971-8263-4875-8b1a-2016b711e99a
  resourceVersion: '4594539'
  generation: 1
  creationTimestamp: '2021-08-04T07:14:24Z'
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: >
      {"apiVersion":"networking.k8s.io/v1","kind":"Ingress","metadata":{"annotations":{},"name":"microbot-ingress","namespace":"default"},"spec":{"rules":[{"host":"microbot.10.0.4.18.nip.io","http":{"paths":[{"backend":{"service":{"name":"microbot","port":{"number":80}}},"path":"/","pathType":"Prefix"}]}}]}}
  managedFields:
    - manager: kubectl-client-side-apply
      operation: Update
      apiVersion: networking.k8s.io/v1
      time: '2021-08-04T07:14:24Z'
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:spec:
          f:rules: {}
    - manager: nginx-ingress-controller
      operation: Update
      apiVersion: networking.k8s.io/v1beta1
      time: '2021-08-04T07:14:27Z'
      fieldsType: FieldsV1
      fieldsV1:
        f:status:
          f:loadBalancer:
            f:ingress: {}
spec:
  rules:
    - host: microbot.10.0.4.18.nip.io
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: microbot
              servicePort: 80
status:
  loadBalancer:
    ingress:
      - ip: 10.0.4.18
      - ip: 10.0.4.19
      - ip: 10.0.4.22

命令查看ingress

 kubectl get ingress
NAME               CLASS    HOSTS                       ADDRESS                         PORTS   AGE
microbot-ingress   <none>   microbot.10.0.4.18.nip.io   10.0.4.18,10.0.4.19,10.0.4.22   80      22h

kubectl describe ingress microbot-ingress
Name:             microbot-ingress
Namespace:        default
Address:          10.0.4.18,10.0.4.19,10.0.4.22
Default backend:  default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
Rules:
  Host                       Path  Backends
  ----                       ----  --------
  microbot.10.0.4.18.nip.io
                             /   microbot:80 (10.1.50.8:80,10.1.89.10:80,10.1.89.9:80)
Annotations:                 <none>
Events:                      <none>

查看namespace

 kubectl get ns
NAME                              STATUS   AGE
default                           Active   33d
ingress-nginx-kubernetes-worker   Active   33d
kube-node-lease                   Active   33d
kube-public                       Active   33d
kube-system                       Active   33d
kubernetes-dashboard              Active   33d

查看namespace default 中pod

kubectl describe pod -n default
Name:         microbot-75cfc77b98-58rqh
Namespace:    default
Priority:     0
Node:         moral-locust/10.0.4.22
Start Time:   Wed, 04 Aug 2021 15:14:25 +0800
Labels:       app=microbot
              pod-template-hash=75cfc77b98
Annotations:  kubernetes.io/psp: privileged
Status:       Running
IP:           10.1.89.9
IPs:
  IP:           10.1.89.9
Controlled By:  ReplicaSet/microbot-75cfc77b98
Containers:
  microbot:
    Container ID:   containerd://fee49d008623358f69f9b772b4389ded608db7d4f57c7065c029ca2a622980bf
    Image:          rocks.canonical.com:443/cdk/cdkbot/microbot-amd64:latest
    Image ID:       rocks.canonical.com:443/cdk/cdkbot/microbot-amd64@sha256:9c949ba3afdb530eaa3a6e6e67126bd7543e4a21b092384e431246dd0141d6c1
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Wed, 04 Aug 2021 15:14:30 +0800
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:80/ delay=5s timeout=30s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-znxkc (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  kube-api-access-znxkc:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:                      <none>


Name:         microbot-75cfc77b98-h2ttn
Namespace:    default
Priority:     0
Node:         moral-locust/10.0.4.22
Start Time:   Wed, 04 Aug 2021 15:14:25 +0800
Labels:       app=microbot
              pod-template-hash=75cfc77b98
Annotations:  kubernetes.io/psp: privileged
Status:       Running
IP:           10.1.89.10
IPs:
  IP:           10.1.89.10
Controlled By:  ReplicaSet/microbot-75cfc77b98
Containers:
  microbot:
    Container ID:   containerd://3ebdee79058a395f5adcab46085a2dfa5334de975cafff65c6f6a56af26e1d8d
    Image:          rocks.canonical.com:443/cdk/cdkbot/microbot-amd64:latest
    Image ID:       rocks.canonical.com:443/cdk/cdkbot/microbot-amd64@sha256:9c949ba3afdb530eaa3a6e6e67126bd7543e4a21b092384e431246dd0141d6c1
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Wed, 04 Aug 2021 15:14:33 +0800
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:80/ delay=5s timeout=30s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-xmxln (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  kube-api-access-xmxln:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:                      <none>


Name:         microbot-75cfc77b98-zt5rx
Namespace:    default
Priority:     0
Node:         crack-raptor/10.0.4.18
Start Time:   Wed, 04 Aug 2021 15:14:25 +0800
Labels:       app=microbot
              pod-template-hash=75cfc77b98
Annotations:  kubernetes.io/psp: privileged
Status:       Running
IP:           10.1.50.8
IPs:
  IP:           10.1.50.8
Controlled By:  ReplicaSet/microbot-75cfc77b98
Containers:
  microbot:
    Container ID:   containerd://6c9a3dcc859e080911a75363cee9b497f3ee7d0f9f0af190ac7bb0687bdc80f6
    Image:          rocks.canonical.com:443/cdk/cdkbot/microbot-amd64:latest
    Image ID:       rocks.canonical.com:443/cdk/cdkbot/microbot-amd64@sha256:9c949ba3afdb530eaa3a6e6e67126bd7543e4a21b092384e431246dd0141d6c1
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Wed, 04 Aug 2021 15:14:33 +0800
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:80/ delay=5s timeout=30s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zz444 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  kube-api-access-zz444:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:                      <none>

编辑本机的 /etc/hosts

vim /etc/hosts

10.0.4.18  microbot.10.0.4.18.nip.io

重启网络服务

netplan apply

测试链接：

curl microbot.10.0.4.18.nip.io

<!DOCTYPE html>
<html>
  <style type="text/css">
    .centered
      {
      text-align:center;
      margin-top:0px;
      margin-bottom:0px;
      padding:0px;
      }
  </style>
  <body>
    <p class="centered"><img src="microbot.png" alt="microbot"/></p>
    <p class="centered">Container hostname: microbot-75cfc77b98-58rqh</p>
  </body>
</html>
root@vivodo-3:~# curl 10.0.4.18
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
Logo
K8S/Kubernetes

K8S/Kubernetes社区为您提供最前沿的新闻资讯和知识内容

更多推荐

【深度】阿里巴巴万级规模 K8s 集群全局高可用体系之美

作者 |  韩堂、柘远、沉醉来源 | 阿里巴巴云原生公众号​前言台湾作家林清玄在接受记者采访的时候，如此评价自己 30 多年写作生涯：“第一个十年我才华横溢，‘贼光闪现’，令周边黯然失色；第二个十年，我终于‘宝光现形’，不再去抢风头，反而与身边的美丽相得益彰；进入第三个十年，繁华落尽见真醇，我进入了‘醇光初现’的阶段，真正体味到了境界之美”。​长夜有穷，真水无香。领略过了 K8s“身在江

avatar K8S/Kubernetes

如何基于 K8s 构建下一代 DevOps 平台？

作者 | 孙健波（天元）导读：当前云原生 DevOps 体系现状如何？面临哪些挑战？如何通过 OAM 解决云原生 DevOps 场景下的诸多问题？云原生开发应用模型 OAM(Open Application Model) 社区核心成员孙健波将为大家一一解答，并分享如何基于 OAM 和 Kubernetes 打造无限能力的下一代 DevOps 平台。什么是 DevOps？为什么基于 Kub

avatar K8S/Kubernetes

k8s 火了！

2020，上云之年，产品云端化成为一种趋势。在一线城市，很多公司都已经构建了自己的私有云环境，比如阿里云、网易云、华为云等。而Kubernetes 作为基于容器编排领域的王者，具备扩展...

avatar K8S/Kubernetes