kubernetes1.17.0集群安装ingress-nginx

最新推荐文章于 2024-04-29 19:25:53 发布
最新推荐文章于 2024-04-29 19:25:53 发布
阅读量1.6k 收藏 1
点赞数 1
分类专栏： kubernetes
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/shiyueshis/article/details/103588228
版权

1.参考列表

https://www.jianshu.com/p/e30b06906b77
https://www.jianshu.com/p/8e3991cedd56
https://www.cnblogs.com/dingbin/p/9754993.html
https://www.cnblogs.com/klvchen/p/9903480.html
https://gitee.com/hmn/ingress-nginx/tree/nginx-0.20.0/deploy
https://www.cnblogs.com/boonya/p/7907999.html
http://www.mamicode.com/info-detail-2825523.html
https://blog.csdn.net/h952520296/article/details/78914036
https://www.xiaoz.me/archives/10578

2.前提

安装了kubernetes集群，参考上篇文章

3.用到的机器（vm模拟）

编号IP配置说明
1192.168.117.1322c2gk8s master节点
2192.168.117.1338c16gk8s node节点
3192.168.117.1341c1gslb节点
4192.168.117.1空win7机器（vmware宿主机）

4.整体架构图

k8s集群整体架构图
其中，LB节点监听80端口，负责TCP 4层转发，代理k8s svc（ingress-nginx）的30080端口。
nginx-ingress-controller即ingress controller，内部也就是一个nginx，k8s中的应用通过创建Ingress类型的对象，修改nginx的配置文件，从而根据Host路由到不同的service。

5.安装ingress controller

kubectl apply -f mandatory.yaml

其中mandatory.yaml的内容是：

apiVersion: v1
kind: Namespace
metadata:
  name: ingress-nginx

---

apiVersion: apps/v1
kind: Deployment
metadata:
  name: default-http-backend
  labels:
    app.kubernetes.io/name: default-http-backend
    app.kubernetes.io/part-of: ingress-nginx
  namespace: ingress-nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: default-http-backend
      app.kubernetes.io/part-of: ingress-nginx
  template:
    metadata:
      labels:
        app.kubernetes.io/name: default-http-backend
        app.kubernetes.io/part-of: ingress-nginx
    spec:
      terminationGracePeriodSeconds: 60
      containers:
        - name: default-http-backend
          # Any image is permissible as long as:
          # 1. It serves a 404 page at /
          # 2. It serves 200 on a /healthz endpoint
          image: registry.cn-qingdao.aliyuncs.com/kubernetes_xingej/defaultbackend-amd64:1.5
          livenessProbe:
            httpGet:
              path: /healthz
              port: 8080
              scheme: HTTP
            initialDelaySeconds: 30
            timeoutSeconds: 5
          ports:
            - containerPort: 8080
          resources:
            limits:
              cpu: 10m
              memory: 20Mi
            requests:
              cpu: 10m
              memory: 20Mi

---
apiVersion: v1
kind: Service
metadata:
  name: default-http-backend
  namespace: ingress-nginx
  labels:
    app.kubernetes.io/name: default-http-backend
    app.kubernetes.io/part-of: ingress-nginx
spec:
  ports:
    - port: 80
      targetPort: 8080
  selector:
    app.kubernetes.io/name: default-http-backend
    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:
      - "extensions"
    resources:
      - ingresses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - events
    verbs:
      - create
      - patch
  - apiGroups:
      - "extensions"
    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:
      serviceAccountName: nginx-ingress-serviceaccount
      containers:
        - name: nginx-ingress-controller
          image: registry.cn-qingdao.aliyuncs.com/kubernetes_xingej/nginx-ingress-controller:0.20.0
          args:
            - /nginx-ingress-controller
            - --default-backend-service=$(POD_NAMESPACE)/default-http-backend
            - --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:
            capabilities:
              drop:
                - ALL
              add:
                - NET_BIND_SERVICE
            # www-data -> 33
            runAsUser: 33
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
          ports:
            - name: http
              containerPort: 80
            - name: https
              containerPort: 443
          livenessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            initialDelaySeconds: 10
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1

---

6.安装一个k8s svc：ingress-nginx，用于暴露pod：nginx-ingress-controller

kubectl apply -f service-nodeport.yaml

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
      nodePort: 30080
    - name: https
      port: 443
      targetPort: 443
      protocol: TCP
      nodePort: 30443
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx

7.安装一个k8s示例应用kubia

kubectl apply -f kubia.yaml

kubia.yaml内容为：

apiVersion: apps/v1
kind: Deployment
metadata:
  name: kubia-web-demo
spec:
  selector:
    matchLabels:
      app: kubia-web-demo
  replicas: 1
  template:
    metadata:
      labels:
        app: kubia-web-demo
    spec:
      containers:
      - name: kubia
        image: registry.cn-hangzhou.aliyuncs.com/jishusc/kubia
        ports:
        - containerPort: 8380
      imagePullSecrets:
      - name: registry-secret
---

apiVersion: v1
kind: Service
metadata:
  name: kubia-web-demo
spec:
  ports:
    - port: 8380
      targetPort: 8380
  selector:
    app: kubia-web-demo

---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kubia-web-demo
spec:
  rules:
  - host: kubia-web.wsc.com
    http:
      paths:
      - path: /
        backend:
          serviceName: kubia-web-demo
          servicePort: 8380

8.测试：通过ingress-nginx svc的nodePort可以访问到kubia应用

8.1 ingress-nginx svc：可以看到通过nodeIP:30080端口可以访问到nginx所在的pod

[root@192 ~]# kubectl get svc -n ingress-nginx 
NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
default-http-backend   ClusterIP   10.96.206.99    <none>        80/TCP                       13h
ingress-nginx          NodePort    10.96.155.148   <none>        80:30080/TCP,443:30443/TCP   89m

8.2 在k8s集群的任一node节点（即在k8s集群内部）上运行curl：可以成功访问到kubia这个应用

[root@192 ~]# curl -H "Host: kubia-web.wsc.com" 192.168.117.132:30080
You have hit kubia-web-demo-6dc9fb9995-j6jrw

8.3 在win7上（即在k8s集群外部）访问kubia应用
配置hosts：其中192.168.117.132机器为k8s master节点所在的机器
192.168.117.132 kubia-web.wsc.com
浏览器访问
在k8s集群外部访问kubia应用

9.在机器192.168.117.134上安装单独的nginx，监听80端口，并转发192.168.117.132:30080的流量（TCP四层转发）

yum install gcc-c++
yum install -y pcre pcre-devel
yum install -y zlib zlib-devel
yum install -y openssl openssl-devel
wget http://nginx.org/download/nginx-1.17.6.tar.gz
./configure --with-stream
make
make install

配置/usr/local/nginx/conf/nginx.conf如下：

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events {
    worker_connections  1024;
}

stream {
     server {
       listen 80;
       proxy_pass 192.168.117.132:30080;
     }
}
http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;


    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    #    listen       8000;
    #    listen       somename:8080;
    #    server_name  somename  alias  another.alias;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}


    # HTTPS server
    #
    #server {
    #    listen       443 ssl;
    #    server_name  localhost;

    #    ssl_certificate      cert.pem;
    #    ssl_certificate_key  cert.key;

    #    ssl_session_cache    shared:SSL:1m;
    #    ssl_session_timeout  5m;

    #    ssl_ciphers  HIGH:!aNULL:!MD5;
    #    ssl_prefer_server_ciphers  on;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}

}

启动nginx

/usr/local/nginx/sbin/nginx

10.最终的测试：在win7机器（k8s集群外部）通过域名访问k8s中的kubia应用

10.1 配置hosts：其中192.168.117.134为nginx所在的机器
192.168.117.134 kubia-web.wsc.com

10.2 浏览器访问
外部访问k8s集群中的应用

shiyueshis
关注
  • 1
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
全网最简单的ingress-nginx安装部署
qq_40657367的博客
11-29 1773
ingress-nginx安装的方式有两种，一种是通过helm安装，另一种是通过ingress官网的提供的yaml文件去安装，本次先以官网的提供的yaml文件文件去安装，后面在出个通过helm安装的教程。这是官网提供的直接通过YAML部署ingress-nginx，一般环境部署在内网情况下的话，这个yaml文件时没法下载的，yaml配置中的pod镜像也没法下载。#部署思路，咱们先把官网提供的部署yaml文件下载下来，在官网的yaml基础上结合咱们当前的环境进行适当的修改。1.先下载官网的yaml配置文件。
Kubernetes 1.19.4安装Nginx-Ingress-Controller
12-17
Kubernetes 1.19.4安装Nginx-Ingress-Controller全套资源 包含以下内容： deploy.yml jettech-kube-webhook-certgen-v1.5.0.tar k8s.gcr.io-ingress-nginx-controller-v0.41.2.tar nginx-1.19.5.tar
k8s安装nginx Ingress超详细指南
一览无遗
04-29 4111
在本全面的Ingress指南中，您将学习如何在 Kubernetes上并使用 DNS 配置 Ingress。目前有两种 Nginx Ingress 控制器。我们将使用 Kubernetes 社区 Nginx 控制器。Ingress & Nginx Ingress 控制器架构下面是使用 Nginx Ingress 控制器的 Kubernetes Ingress 的高级架构。在本指南中，我们将学习如何在体系结构中构建设置。​先决条件。
kubernetes安装ingress-nginx过程记录——＜04＞
CEVERY的博客
10-13 391
一、安装前注意事项 1、ingress-controler可以根据情况创建在任一个命名空间下 2、若应用在不同的域名空间下，则需要创建不同的ingress，否则，访问其它域名空间下的应用会出现503错误 二、开始安装 1、创建 mandatory-default.yaml 文件 此处命名空间是default apiVersion: v1 kind: Namespace metadata: name: ingress-nginx labels: app.kubernetes.io/name:
Kubernetes1.18.3 使用ingress
yyl的博客
06-24 1557
Kubernetes1.18.3 使用ingress 1-下载配置文件包 链接: github下载 百度网盘 2-找到deploy文件夹下7个yaml文件提取出来 3-分别修改default-backend.yaml和with-rbac.yaml 4-创建 kubectl create -f namespace.yaml kubectl create -f default-backend.yaml kubectl create -f configmap.yaml kubectl create -f t
k8s-nginx-ingress-1
kxq的博客
01-03 377
启动ingress 1.官网下载yaml,官网地址：https://kubernetes.github.io/ 也就是去官网复制下面两句话，并在主节点上运行： 复制yaml（应该算是deployment部分）： kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/stat...
【K8S】部署ingress
非晓为骁的博客
10-15 861
k8s如何部署ingress
annoy-1.17.0-cp38-cp38-win_amd64
08-19
annoy-1.17.0-cp38-cp38-win_amd64
annoy-1.17.0-cp37-cp37m-win_amd64
08-19
annoy-1.17.0-cp37-cp37m-win_amd64
annoy-1.17.0-pp37-pypy37_pp73-win_amd64
08-19
annoy-1.17.0-pp37-pypy37_pp73-win_amd64
Python库 | numpy-1.17.0-cp37-cp37m-manylinux1_x86_64.whl
05-08
资源分类：Python库 所属语言：Python 资源全名：numpy-1.17.0-cp37-cp37m-manylinux1_x86_64.whl 资源来源：官方 安装方法：https://lanzao.blog.csdn.net/article/details/101784059
AlexaPy-1.17.0-py3-none-any.whl.zip
最新发布
05-27
本篇文章将围绕"AlexaPy-1.17.0-py3-none-any.whl.zip"这个压缩包文件，详细讲解如何安装AlexaPy库以及利用其进行技能开发。 首先，我们看到文件名为"AlexaPy-1.17.0-py3-none-any.whl"，这是一个Python的wheel格式...
K8S集群安装Ingress-Nginx
qq_37705525的博客
05-11 2735
K8S集群安装Ingress-Nginx
k8s 安装 ingress-nginx
mingqing的博客
08-31 5663
k8s 安装 ingress-nginx
k8s 中 ingress的安装及配置
bjsunwei的博客
12-22 2340
ingress 服务在k8s中也是以后台pod的形式存在，需要安装nginx-ingress-controller的镜像。 需要单独建立ingress的service，防火墙上发布应用，针对的是次service的端口。 ingress上发布应用，需要新增单独的ingress配置，配置域名、端口、后台对应的service
k8s部署ingress-nginx的方法步骤
热门推荐
a13568hki的博客
04-28 1万+
1. ingress概述 我们知道service的表现形式为IP:PORT，即工作在第四层传输层（TCP/IP层），那么对于不同的URL地址经常对应用不同的后端服务或者虚拟服务器，这些应用层的转发机制仅通过kubernetes的service机制是无法实现的，这种情况我们可以使用ingress策略定义和一个具体的ingress Controller，两者结合实现一个完整的Ingress 负载均衡，这个负载均衡是基于nginx七层反向代理来实现。 k8s 对外暴露服务（service）主要有两种方式：Note
kubernetes部署Ingress-nginx
IT
01-05 7182
Pod的IP以及service IP只能在集群内访问，如果想在集群外访问kubernetes提供的服务，可以使用nodeport、proxy、loadbalacer以及ingress等方式，由于service的IP集群外不能访问，可以使用ingress方式再代理一次，即ingress代理service，service代理pod。
k8s v1.16.2中部署ingress-nginx
Rainsome的专栏
10-28 2257
环境与软件版本 OS Centos 7 软件 ingress-nginx https://github.com/kubernetes/ingress-nginx (commit:43fa61cabdba39f81c0f3d38edc8bdb5892027f1) k8s 使用kubeadm部署k8s(v1.16.2) 安装 修改配置文件 修改deploy/baremetal/service-node...
numpy-1.17.0-cp36-cp36m-win_amd64.whl
12-07
numpy-1.17.0-cp36-cp36m-win_amd64.whl 是一个用于 Windows 操作系统上的 numpy 库的安装文件。其中，1.17.0 表示 numpy 的版本号，cp36 表示该文件适用于 Python 3.6 版本，win_amd64 表示该文件适用于 64 位的 ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值