AI导航网
微信公众号搜"智元新知"关注
微信扫一扫可直接关注哦！

k8s之Service详解-Ingress使用

分类：k8s作者：编程之家原文地址

环境准备

搭建ingress环境

#创建文件夹
[root@master ~]# mkdir ingress-controller
[root@master ~]# cd ingress-controller/
[root@master ingress-controller]# 

#获取ingress-Nginx，本次案例使用的是0.30版本（不挂代理可能无法访问，这里我把yaml文件内容复制上来，需要的可以自行复制粘贴）
[root@master ingress-controller]# wget https://raw.githubusercontent.com/kubernetes/ingress-Nginx/Nginx-0.30.0/deploy/static/mandatory.yaml
[root@master ingress-controller]# wget https://raw.githubusercontent.com/kubernetes/ingress-Nginx/Nginx-0.30.0/deploy/static/provider/bareMetal/service-nodeport.yaml
[root@master ingress-controller]# ls
mandatory.yaml service-nodeport.yaml

mandatory.yaml

apiVersion: v1
kind: Namespace
Metadata:
  name: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---

kind: ConfigMap
apiVersion: v1
Metadata:
  name: Nginx-configuration
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
kind: ConfigMap
apiVersion: v1
Metadata:
  name: tcp-services
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
kind: ConfigMap
apiVersion: v1
Metadata:
  name: udp-services
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
apiVersion: v1
kind: ServiceAccount
Metadata:
  name: nginx-ingress-serviceaccount
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
Metadata:
  name: nginx-ingress-clusterrole
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
rules:
  - apiGroups:
      - ""
    resources:
      - configmaps
      - endpoints
      - nodes
      - pods
      - secrets
    verbs:
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - nodes
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - services
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - events
    verbs:
      - create
      - patch
  - apiGroups:
      - "extensions"
      - "networking.k8s.io"
    resources:
      - ingresses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - "extensions"
      - "networking.k8s.io"
    resources:
      - ingresses/status
    verbs:
      - update

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
Metadata:
  name: nginx-ingress-role
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
rules:
  - apiGroups:
      - ""
    resources:
      - configmaps
      - pods
      - secrets
      - namespaces
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - configmaps
    resourceNames:
      # Defaults to "<election-id>-<ingress-class>"
      # Here: "<ingress-controller-leader>-<Nginx>"
      # This has to be adapted if you change either parameter
      # when launching the nginx-ingress-controller.
      - "ingress-controller-leader-Nginx"
    verbs:
      - get
      - update
  - apiGroups:
      - ""
    resources:
      - configmaps
    verbs:
      - create
  - apiGroups:
      - ""
    resources:
      - endpoints
    verbs:
      - get

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: RoleBinding
Metadata:
  name: nginx-ingress-role-nisa-binding
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: nginx-ingress-role
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: ingress-Nginx

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
Metadata:
  name: nginx-ingress-clusterrole-nisa-binding
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: nginx-ingress-clusterrole
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: ingress-Nginx

---

apiVersion: apps/v1
kind: Deployment
Metadata:
  name: nginx-ingress-controller
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: ingress-Nginx
      app.kubernetes.io/part-of: ingress-Nginx
  template:
    Metadata:
      labels:
        app.kubernetes.io/name: ingress-Nginx
        app.kubernetes.io/part-of: ingress-Nginx
      annotations:
        prometheus.io/port: "10254"
        prometheus.io/scrape: "true"
    spec:
      # wait up to five minutes for the drain of connections
      terminationGracePeriodSeconds: 300
      serviceAccountName: nginx-ingress-serviceaccount
      nodeselector:
        kubernetes.io/os: linux
      containers:
        - name: nginx-ingress-controller
          image: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.30.0
          args:
            - /nginx-ingress-controller
            - --configmap=$(POD_NAMESPACE)/Nginx-configuration
            - --tcp-services-configmap=$(POD_NAMESPACE)/tcp-services
            - --udp-services-configmap=$(POD_NAMESPACE)/udp-services
            - --publish-service=$(POD_NAMESPACE)/ingress-Nginx
            - --annotations-prefix=Nginx.ingress.kubernetes.io
          securityContext:
            allowPrivilegeEscalation: true
            capabilities:
              drop:
                - ALL
              add:
                - NET_BIND_SERVICE
            # www-data -> 101
            runAsUser: 101
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldpath: Metadata.name
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldpath: Metadata.namespace
          ports:
            - name: http
              containerPort: 80
              protocol: TCP
            - name: https
              containerPort: 443
              protocol: TCP
          livenessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            initialDelaySeconds: 10
            periodSeconds: 10
            successthreshold: 1
            timeoutSeconds: 10
          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            periodSeconds: 10
            successthreshold: 1
            timeoutSeconds: 10
          lifecycle:
            preStop:
              exec:
                command:
                  - /wait-shutdown

---

apiVersion: v1
kind: LimitRange
Metadata:
  name: ingress-Nginx
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
spec:
  limits:
  - min:
      memory: 90Mi
      cpu: 100m
    type: Container
View Code

 service-nodeport.yaml

apiVersion: v1
kind: Service
Metadata:
  name: ingress-Nginx
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
spec:
  type: NodePort
  ports:
    - name: http
      port: 80
      targetPort: 80
      protocol: TCP
    - name: https
      port: 443
      targetPort: 443
      protocol: TCP
  selector:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
View Code 
#创建ingress-Nginx
[root@master ingress-controller]# kubectl apply -f ./
namespace/ingress-Nginx created
configmap/Nginx-configuration created
configmap/tcp-services created
configmap/udp-services created
serviceaccount/nginx-ingress-serviceaccount created
clusterrole.rbac.authorization.k8s.io/nginx-ingress-clusterrole created
role.rbac.authorization.k8s.io/nginx-ingress-role created
rolebinding.rbac.authorization.k8s.io/nginx-ingress-role-nisa-binding created
clusterrolebinding.rbac.authorization.k8s.io/nginx-ingress-clusterrole-nisa-binding created
deployment.apps/nginx-ingress-controller created
limitrange/ingress-Nginx created
service/ingress-Nginx created

#查看ingress-Nginx
[root@master ingress-controller]# kubectl get pod -n ingress-Nginx
NAME                                        READY   STATUS    RESTARTS   AGE
nginx-ingress-controller-7f74f657bd-kzvrq   1/1     Running   0          2m7s

#查看service
[root@master ingress-controller]# kubectl get svc -n ingress-Nginx
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-Nginx NodePort 10.106.160.9 <none> 80:32000/TCP,443:32421/TCP 5m48s

准备service和pod

为了方便后续的实验，创建下图所示的模型

 

创建tomcat-Nginx.yaml

apiVersion: apps/v1
kind: Deployment
Metadata: 
  name: Nginx-deployment
  namespace: dev
spec:
  replicas: 3
  selector:
    matchLabels:
      app: Nginx-pod
  template:
    Metadata:
      labels:
        app: Nginx-pod
    spec:
      containers:
      - name: Nginx
        image: Nginx:1.17.1
        ports: 
        - containerPort: 80

---

apiVersion: apps/v1
kind: Deployment
Metadata: 
  name: tomcat-deployment
  namespace: dev
spec:
  replicas: 3
  selector:
    matchLabels:
      app: tomcat-pod
  template:
    Metadata:
      labels:
        app: tomcat-pod
    spec:
      containers:
      - name: tomcat
        image: tomcat:8.5-jre10-slim
        ports: 
        - containerPort: 8080

---

apiVersion: v1
kind: Service
Metadata: 
  name: Nginx-service
  namespace: dev
spec:
  selector:
    app: Nginx-pod
  clusterIP: None
  type: ClusterIP
  ports:
  - port: 80
    targetPort: 80

---

apiVersion: v1
kind: Service
Metadata: 
  name: tomcat-service
  namespace: dev
spec:
  selector:
    app: tomcat-pod
  clusterIP: None
  type: ClusterIP
  ports:
  - port: 8080
    targetPort: 8080
View Code

使用配置文件

[root@master ingress-controller]# cd ..
[root@master ~]# vim tomcat-Nginx.yaml
[root@master ~]# kubectl create -f tomcat-Nginx.yaml 
deployment.apps/Nginx-deployment created
deployment.apps/tomcat-deployment created
service/Nginx-service created
service/tomcat-service created
[root@master ~]# kubectl get svc -n dev
NAME             TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)    AGE
Nginx-service    ClusterIP   None         <none>        80/TCP     20s
tomcat-service   ClusterIP   None         <none>        8080/TCP   20s

Http代理

创建ingress-http.yaml

apiVersion: extensions/v1beta1
kind: Ingress
Metadata:
  name: ingress-http
  namespace: dev
spec:
  rules:
  - host: Nginx.test.com
    http:
      paths:
      - path: /
        backend:
          serviceName: Nginx-service
          servicePort: 80
  - host: tomcat.test.com
    http:
      paths:
      - path: /
        backend:
          serviceName: tomcat-service
          servicePort: 8080

使用配置文件

[root@master ~]# vim ingress-http.yaml

[root@master ~]# kubectl create -f ingress-http.yaml 
ingress.extensions/ingress-http created

[root@master ~]# kubectl get ing ingress-http -n dev
NAME           HOSTS                            ADDRESS   PORTS   AGE
ingress-http   Nginx.test.com,tomcat.test.com             80      13s

[root@master ~]# kubectl describe ing ingress-http -n dev
Name:             ingress-http
Namespace:        dev
Address:          10.106.160.9
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host             Path  Backends
  ----             ----  --------
  Nginx.test.com   
                   /   Nginx-service:80 (10.244.1.33:80,10.244.2.13:80,10.244.2.16:80)
  tomcat.test.com  
                   /   tomcat-service:8080 (10.244.2.14:8080,10.244.2.17:8080,10.244.2.18:8080)
Annotations:
  kubectl.kubernetes.io/last-applied-configuration:  {"apiVersion":"extensions/v1beta1","kind":"Ingress","Metadata":{"annotations":{},"name":"ingress-http","namespace":"dev"},"spec":{"rules":[{"host":"Nginx.test.com","http":{"paths":[{"backend":{"serviceName":"Nginx-service","servicePort":80},"path":"/"}]}},{"host":"tomcat.test.com","http":{"paths":[{"backend":{"serviceName":"tomcat-service","servicePort":8080},"path":"/"}]}}]}}

Events:
  Type    Reason  Age                From                      Message
  ----    ------  ----               ----                      -------
  normal  CREATE  18m                nginx-ingress-controller  Ingress dev/ingress-http
  normal  UPDATE  38s (x2 over 18m)  nginx-ingress-controller  Ingress dev/ingress-http

 

修改本机的hosts文件（位置：C:\Windows\System32\drivers\etc），添加如下内容

master虚拟机的IP地址    Nginx.test.com
masete虚拟机的IP地址    tomcat.test.com

查看ingress为service提供的端口号

[root@master ~]# kubectl get svc -n ingress-Nginx
NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
ingress-Nginx   NodePort   10.106.160.9   <none>        80:32000/TCP,443:32421/TCP   95m

在浏览器中测试访问,发现能够访问通

Nginx：

 

 tomcat：

 

Https代理

创建证书

[root@master ~]# openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj "/C=CN/ST=BJ/L=BJ/O=Nginx/CN=test.com"
Generating a 2048 bit RSA private key
............................+++
..............................+++
writing new private key to 'tls.key'
-----

创建密钥

[root@master ~]# kubectl create secret tls tls-secret --key tls.key --cert tls.crt
secret/tls-secret created

创建ingress-https.yaml

apiVersion: extensions/v1beta1
kind: Ingress
Metadata:
  name: ingress-https
  namespace: dev
spec:
  tls:
    - hosts:
      - Nginx.test.com
      - tomcat.test.com
      secretName: tls-secret  #指定密钥
  rules:
  - host: Nginx.test.com
    http:
      paths:
      - path: /
        backend:
          serviceName: Nginx-service
          servicePort: 80
  - host: tomcat.test.com
    http:
      paths:
      - path: /
        backend:
          serviceName: tomcat-service
          servicePort: 8080

使用配置文件

[root@master ~]# vim ingress-https.yaml
[root@master ~]# kubectl create -f ingress-https.yaml 
ingress.extensions/ingress-https created

[root@master ~]# kubectl get ing ingress-https -n dev
NAME            HOSTS                            ADDRESS        PORTS     AGE
ingress-https   Nginx.test.com,tomcat.test.com   10.106.160.9   80, 443   52s

[root@master ~]# kubectl describe ing ingress-https -n dev
Name:             ingress-https
Namespace:        dev
Address:          10.106.160.9
Default backend:  default-http-backend:80 (<none>)
TLS:
  tls-secret terminates Nginx.test.com,tomcat.test.com
Rules:
  Host             Path  Backends
  ----             ----  --------
  Nginx.test.com   
                   /   Nginx-service:80 (10.244.1.33:80,10.244.2.13:80,10.244.2.16:80)
  tomcat.test.com  
                   /   tomcat-service:8080 (10.244.2.14:8080,10.244.2.17:8080,10.244.2.18:8080)
Annotations:
Events:
  Type    Reason  Age   From                      Message
  ----    ------  ----  ----                      -------
  normal  CREATE  79s   nginx-ingress-controller  Ingress dev/ingress-https
  normal  UPDATE  38s   nginx-ingress-controller  Ingress dev/ingress-https

获取端口，左边的是http使用的端口，右边是https使用的端口，因此要使用的端口是32421

[root@master ~]# kubectl get svc -n ingress-Nginx
NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
ingress-Nginx   NodePort   10.106.160.9   <none>        80:32000/TCP,443:32421/TCP   129m

使用浏览器访问

Nginx:

 

tomcat:

 

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 [email protected] 举报，一经查实，本站将立刻删除。

相关推荐

Kubernetes(k8s)部署Redis cluster集群
Redis Cluster 提供了一种运行 Redis 安装的方法，其中数据&#160;在多个 Redis 节点之间自动分片。 Redis Cluster 还在分区期间提供了一定程度的可用性，这实际上是在某些节点出现故障或无法通信时继续操作的能力...
GitLab集成kubernetes实现自动发布
创建GitLab源码项目并上传示例代码 1. 创建GitLab源码项目 本示例中创建的GitLab源码项目地址为：https://gitee.com/SunHarvey/helloworld_java.git 2. 执行以下命令获取示例代码并上传至GitLab git clone https://g
从零开始掌握Kubernetes: Pod和Deployment的幕后故事
1. 引言 在如今的技术世界中，随着微服务架构的广泛应用和云原生理念的兴起，应用程序的开发、部署和管理发生了翻天覆地的变化。容器技术的出现使得开发者可以轻松地将应用及其所有依赖打包在一个轻量级、可移植的容...
轻量级日志收集方案Loki
先看看结果有多轻量吧 官方文档：https://grafana.com/docs/loki/latest/ 简介 Grafana Loki 是一个日志聚合工具，它是功能齐全的日志堆栈的核心。 Loki 是一个为有效保存日志数据而优化的数据存储。日志数据的高效索...
安装Kubernetes(k8s)保姆级教程---无坑版
一、安装环境说明 硬件要求 内存：2GB或更多RAM CPU: 2核CPU或更多CPU 硬盘: 30GB或更多 本次环境说明： 操作系统：CentOS 7.9 内核版本：3.10.0-1160 master： 192.168.68.106 node01： 192.168.68.107 node02：
CentOS7部署ceph
CEPH 简介 不管你是想为云平台提供Ceph 对象存储和/或 Ceph 块设备，还是想部署一个 Ceph 文件系统或者把 Ceph 作为他用，所有 Ceph 存储集群的部署都始于部署一个个 Ceph 节点、网络和 Ceph 存储集群。 Ceph 存储集...
k8s怎么给node添加标签
这篇文章主要介绍“k8s怎么给node添加标签”的相关知识，小编通过实际案例向大家展示操作过程，操作方法简单快捷，实用性强，希望这篇“k8s怎么给node添加标签”...
K8s超详细安装部署流程
例如：随着人工智能的不断发展，机器学习这门技术也越来越重要，很多人都开启了学习机器学习，本文就介绍了机器学习的基础内容。提示：以下是本篇文章正文内容，下面案例可供参考例如：以上就是今天要讲的内容，本文...
failed to find plugin “flannel” in path [/opt/cni/bin]，k8sNotReady解决方案
failed to find plugin “flannel” in path [/opt/cni/bin]，k8sNotReady解决方案
【云原生 · k8s】k8s-master初始化过程讲解
2、k8s-master运行的组件查看，控制平面（官网说法）查看构成k8s主节点。查看 k8s集群状态，查看有哪些工作节点此时node机器就可以和master机器 通信 了，走kubelet进程该进程是以什么形式运行的？宿主机直接，以1号...
    pythonJavaScriptjavaHTMLreactjsC#AndroidCSSNode.jssqlrpython-3.xMysqLjQueryc++pandasFlutterangularIOSdjangolinuxswifttypescript路由器JSON路由器设置无线路由器h3c华三华三路由器设置华三路由器电脑软件教程arraysdocker软件图文教程Cvue.jslaravelspring-bootreact-native