kubernetes 1.18 部署 ingress-nginx

最新推荐文章于 2023-10-01 15:47:11 发布
最新推荐文章于 2023-10-01 15:47:11 发布
阅读量903 收藏 1
点赞数
分类专栏： kubernetes 文章标签： kubernetes 容器 ingress-nginx ingress
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/d1179869625/article/details/128235603
版权

文章目录

kubernetes 1.18 部署 ingress-nginx

1. 下载 yaml 文件

在 GitHub 下载完成之后可以直接使用，不需要修改文件内容，如果下载不了也可直接粘贴本文中内容

  • mandatory.yaml
wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/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
  • service-nodeport.yaml
wget  https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/provider/baremetal/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

---

2. 安装 ingress-nginx

kubectl apply -f mandatory.yaml 

[root@master ~]# kubectl apply -f mandatory.yaml 
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
namespace/ingress-nginx configured
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

kubectl apply -f service-nodeport.yaml 

[root@master ~]# kubectl apply -f service-nodeport.yaml 
service/ingress-nginx created

3. 检查安装情况

[root@master ~]# kubectl get pods,svc,deployment -n ingress-nginx
NAME                                            READY   STATUS    RESTARTS   AGE
pod/nginx-ingress-controller-5bb8fb4bb6-jsrql   1/1     Running   0          18m

NAME                    TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
service/ingress-nginx   NodePort   10.103.232.28   <none>        80:32731/TCP,443:30422/TCP   17m

NAME                                       READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/nginx-ingress-controller   1/1     1            1           18m

4. 测试验证

准备两个测试的 pod ，并同时创建他们的 service 网络

1️⃣ 准备一个 hello-world 镜像，并使用他的 9000 端口，创建一个 service hello-server 并将 9000 端口指向对外暴露的 8000 端口

2️⃣ nginx 镜像也是同样的操作

apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-server
spec:
  replicas: 2
  selector:
    matchLabels:
      app: hello-server
  template:
    metadata:
      labels:
        app: hello-server
    spec:
      containers:
      - name: hello-server
        image: registry.cn-hangzhou.aliyuncs.com/lfy_k8s_images/hello-server	# 这里使用的尚硅谷的一个案例，后期可能会不能访问，也可以使用其他的镜像源进行测试
        ports:
        - containerPort: 9000
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: nginx-demo
  name: nginx-demo
spec:
  replicas: 2
  selector:
    matchLabels:
      app: nginx-demo
  template:
    metadata:
      labels:
        app: nginx-demo
    spec:
      containers:
      - image: nginx
        name: nginx
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app: nginx-demo
  name: nginx-demo
spec:
  selector:
    app: nginx-demo
  ports:
  - port: 8000
    protocol: TCP
    targetPort: 80
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app: hello-server
  name: hello-server
spec:
  selector:
    app: hello-server
  ports:
  - port: 8000
    protocol: TCP
    targetPort: 9000

3️⃣ 配置 ingress 规则

apiVersion: extensions/v1beta1		# 1.18 版本与新版本的 api 是不一样的
kind: Ingress
metadata:
  name: ingress-http
spec:
  ingressClassName: nginx
  rules:
  - host: hello.demo.com
    http:
      paths:
      - pathType: Prefix
        path: /
        backend:
          serviceName: hello-server		# 这个 hello-server 一定要和对应的 service 的名称相同，但是这里的参数变成了 serviceName，与上面 1.23 版本是不同的，下面的 nginx 同理。
          servicePort: 8000
  - host: nginx.demo.com
    http:
      paths:
      - pathType: Prefix
        path: /
        backend:
          serviceName: nginx-demo
          servicePort: 8000

4.1 查看ingress规则

[root@master ~]# kubectl get ingress
NAME               CLASS   HOSTS                           ADDRESS           PORTS   AGE
ingress-host-bar   nginx   hello.demo.com,nginx.demo.com   192.168.169.161   80      71m

4.2 访问测试

个人测试时可以将域名配置在 C:\Windows\System32\drivers\etc 的 hosts 文件中
示例：这里的 ip 配置集群中的任意 node ip 都可以
192.168.169.161 hello.demo.com
192.168.169.161 nginx.demo.com

查看 ingress-nginx service 的端口号，80和443分别对应不同的端口

[root@master ~]# kubectl get svc -n ingress-nginx
NAME                                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx-controller             NodePort    10.96.103.255   <none>        80:30050/TCP,443:30580/TCP   10h

http://nginx.demo.com:30050/
在这里插入图片描述

5. 其他内容

本文参考：https://blog.csdn.net/a13568hki/article/details/124452407
更多其他内容可参考https://blog.csdn.net/D1179869625/article/details/128140619

 
 
 
 
 

Direct_
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.20.0镜像包
03-06
kubernetes的quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.20.0镜像包，版本为v0.20.0。文件先解压，之后得到nginx-ingress-controller.0.20.0.tar
使用 kubeadm 安装单master kubernetes 集群（脚本版）
Mo小泽的技术博客
09-22 2382
文章目录使用 kubeadm 安装单master kubernetes 集群配置要求检查 centos / hostname检查网络安装docker及kubelet初始化 master 节点初始化 worker节点获得 join命令参数初始化worker常见错误原因worker 节点不能访问 apiserverworker 节点默认网卡移除worker节点并重试检查初始化结果安装 Ingress Controller 使用 kubeadm 安装单master kubernetes 集群 配置要求 对于 Ku
kubernetes v1.18的ingress-nginx 0.30.0分支最新版本部署
码农崛起
02-19 2000
1、ingress介绍 K8s集群对外暴露服务的方式目前只有三种：Loadblancer；Nodeport；ingress 前两种熟悉起来比较快，而且使用起来也比较方便，在此就不进行介绍了。 下面详细讲解下ingress这个服务，ingress由两部分组成： ingress controller：将新加入的Ingress转化成Nginx的配置文件并使之生效 ingress服务：将Nginx的配置抽象成一个Ingress对象，每添加一个新的服务只需写一个新的Ingress的yaml文件即可 其中ing
kubernetes v1.18的ingress-nginx 0.30.0最新版本部署
风口向上的博客
08-18 3124
一、部署配置Ingress controller 1、配置ingress-nginx yaml部署文件 [root@k8s-node01 ingress-nginx]# vi mandatory.yaml apiVersion: v1 kind: Namespace metadata: name: ingress-nginx labels: app.kubernetes.io/name: ingress-nginx app.kubernetes.io/part-of: ingress
云原生|kubernetes|ingress-nginx插件部署以及简单的应用（修订版---适用于kubernetes-1.18-1.21）
zsk_john的技术分享专用博客
10-03 1961
【代码】云原生|kubernetes|ingress-nginx插件部署以及简单的应用。
k8s部署ingress-nginx步骤
weixin_48878440的博客
04-21 3527
k8s部署ingress应用 部署ingress 部署ingress-nginx ingress详细解析
Ingress-Nginx（0.30.0）在k8s集群内的配置
炙风的博客
11-19 1254
前言 如果kubernetes集群决定使用Ingress-Nginx七层负载均衡，那么可以参考本教程。 准备 一台能访问互联网的PC。 一个完整的k8s集群 。 一个待被负载的应用。 最好有一个docker私有仓库。 步骤 一、组件准备 1.1. 首先打开github的Ingress-Nginx仓库，如图找到nginx-0.30.0 1.2. 访问deploy文件夹 1.3.打开文档 1.4.直接在k8s主节点执行此语句。 kubectl apply -f https://raw.githubu
Kubernetes1.18.3 使用ingress
yyl的博客
06-24 1539
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
【kubernetes】kubernetes中的Ingress使用
追寻梦想的青春
10-01 622
Service作为一组Pod对外提供服务的载体，当外部需要访问这组Pod时只需要通过ServiceName和ServicePort进行访问，不需要关心该Service后面的Pod，而ServiceName和ServicePort是固定的，通过这种方式就将一组可变的Pod提供的业务功能变成了对ServiceName和ServicePort的访问。这里有两个端口，port：服务的端口，在集群内部可以通过service和port访问，只做映射，targetPort：目标端口，容器中的应用监听的端口。
k8s helm 无坑部署ingress-nginx
weixin_43909790的博客
08-29 2818
helm 部署ingress-nginx，以及ingress的使用
ingress-nginx-controller-1.9.yaml
10-18
三处image需要修改（若官方deplo.yaml中的image可以拉取，则不需要改image），另两个文件是测试ingress规则是否生效的yaml。
ingress-nginx部署文件，用于k8s部署ingress-nginx服务
最新发布
04-15
ingress-nginx部署文件，用于k8s部署ingress-nginx服务
ingress-nginx-controller（含镜像和代码）.rar
10-28
这个使用方法去这篇博客：https://cuichongxin.blog.csdn.net/article/details/120184717
k8s-修改ingress-nginx-controller中nginx配置文件参数参考
07-20
k8s-修改ingress-nginx-controller中nginx配置文件参数参考
Kubernetes1.18.3 部署nginx-ingress
wuxingge的博客
09-30 340
参考 https://blog.csdn.net/hzh839900/article/details/107696118 下载nginx-ingress包 https://github.com/kubernetes/ingress-nginx/archive/nginx-0.11.0.tar.gz 修改default-backend.yaml，修改镜像地址 修改with-rbac.yaml，修改镜像地址，deployment修改为Daemonset 创建nginx-ingress服务 vim service
k8s安装ingress
blues的博客
06-29 2464
版本介绍 组件 版本 k8s v1.18 ingress 0.30.0 1. 下载两个文件 https://github.com/kubernetes/ingress-nginx/blob/nginx-0.30.0/deploy/static/mandatory.yaml https://github.com/kubernetes/ingress-nginx/blob/nginx-0.30.0/deploy/baremetal/service-nodeport.yaml 2. 在k...
k8s之ingress
snail_youth的博客
03-25 754
k8s下安装ingress，且对nodeport模式进行测试。
烂泥：k8s安装与配置ingress(一)
weixin_33816611的博客
05-11 1095
2019独角兽企业重金招聘Python工程师标准>>> ...
k8s 1.25部署ingress-nginx需要修改的
06-06
K8s 1.25部署Ingress-nginx需要修改以下几个方面： 首先，需要修改Kubernetes控制平面的打开http访问的端口，让Ingress-nginx可以通过控制平面的端口访问到API Server。可以通过以下命令打开端口80： ``` sudo kubeadm init phase control-plane apiserver --apiserver-args insecure-port=80 ``` 然后，需要添加Ingress-nginx的helm chart仓库。通过以下命令可以添加： ``` helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update ``` 接下来，需要安装Ingress-nginx的helm chart。可以通过以下命令来进行安装： ``` helm install ingress-nginx ingress-nginx/ingress-nginx ``` 最后，需要安装Ingress-nginx的配置文件。可以通过以下命令来进行安装： ``` kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.1/deploy/static/provider/baremetal/deploy.yaml ``` 这些都是K8s 1.25部署Ingress-nginx需要修改的地方。除了上述修改点，还需要注意处理相应的网络配置以及对Ingress-nginx的调优和安全控制等方面的工作。

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值