ingress

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

image.png

部署ingress-controller

https://blog.csdn.net/networken/article/details/85881558
https://www.cnblogs.com/dingbin/p/9754993.html

下载nginx-ingress-controller配置文件

wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.21.0/deploy/mandatory.yaml

修改镜像地址

image: willdockerhub/nginx-ingress-controller:0.21.0

image: 10.0.0.11:5000/wuxingge/nginx-ingress-controller:0.21.0

[root@k8s-master1 ingree-nginx]# vim nginx-ingress.yaml

apiVersion: v1
kind: Namespace
metadata:
  name: 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

---
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: extensions/v1beta1
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: 192.168.0.141:5000/wuxingge/nginx-ingress-controller:0.21.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:
            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

---

执行yaml文件部署

kubectl create -f nginx-ingress.yaml

[root@k8s-master1 ingree-nginx]# kubectl get pods -o wide -n ingress-nginx
NAME                                       READY   STATUS    RESTARTS   AGE   IP            NODE        NOMINATED NODE   READINESS GATES
nginx-ingress-controller-c9b47ff67-7pwqh   1/1     Running   0          89s   10.254.40.4   10.0.0.12   <none>           <none>

nodeport方式对外提供服务

通过ingress-controller对外提供服务，现在还需要手动给ingress-controller建立一个servcie，接收集群外部流量。

service-nodeport配置文件

wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/baremetal/service-nodeport.yaml

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

执行

kubectl create -f service-nodeport.yaml

查看

[root@k8s-master1 ingree-nginx]# kubectl get service -n ingress-nginx 
NAME            TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.254.150.28   <none>        80:30080/TCP,443:30443/TCP   8s

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

使用Ingress发布tomcat

准备名称空间

vi testing-namespace.yaml

kind: Namespace
apiVersion: v1
metadata:
  name: testing
  labels:
    env: testing

[root@k8s-master1 ingree-nginx]# kubectl create -f testing-namespace.yaml 
namespace/testing created
[root@k8s-master1 ingree-nginx]# kubectl get namespaces testing 
NAME      STATUS   AGE
testing   Active   21s

部署tomcat实例

vi tomcat-deploy.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: tomcat-deploy
  namespace: testing
spec:
  replicas: 2
  selector:
    matchLabels:
      app: tomcat
  template:
    metadata:
      labels:
        app: tomcat
    spec:
      containers:
      - name: tomcat
        image: tomcat:8.0.50-jre8-alpine
        ports:
        - containerPort: 8080
          name: httpport
        - containerPort: 8009
          name: ajpport

kubectl create -f  tomcat-deploy.yaml

[root@k8s-master1 ingree-nginx]# kubectl get pods -n testing -o wide
NAME                             READY   STATUS    RESTARTS   AGE     IP             NODE        NOMINATED NODE   READINESS GATES
tomcat-deploy-5c55c48479-mxfgv   1/1     Running   0          6m55s   10.254.88.5    10.0.0.12   <none>           <none>
tomcat-deploy-5c55c48479-wswjl   1/1     Running   0          7m40s   10.254.102.2   10.0.0.13   <none>           <none>

创建Service资源

vi tomcat-svc.yaml

apiVersion: v1
kind: Service
metadata:
  name: tomcat-svc
  namespace: testing
  labels:
    app: tomcat-svc
spec:
  selector:
    app: tomcat
  ports:
  - name: http
    port: 80
    targetPort: 8080
    protocol: TCP

[root@k8s-master1 ingree-nginx]# kubectl create -f  tomcat-svc.yaml
service/tomcat-svc created
[root@k8s-master1 ingree-nginx]# kubectl get service -n testing -o wide
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE   SELECTOR
tomcat-svc   ClusterIP   10.254.198.130   <none>        80/TCP    25s   app=tomcat

创建Ingress资源

vi tomcat-ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: tomcat
  namespace: testing
  annotations:
    kubernetes.io/ingress.class: "nginx"
spec:
  rules:
  - host: tomcat.wuxingge.com
    http:
      paths:
      - path:
        backend:
          serviceName: tomcat-svc
          servicePort: 80

kubectl create -f  tomcat-ingress.yaml

[root@k8s-master1 ingree-nginx]# kubectl describe ingresses.extensions -n testing 
Name:             tomcat
Namespace:        testing
Address:          
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host                 Path  Backends
  ----                 ----  --------
  tomcat.wuxingge.com  
                          tomcat-svc:80 (<none>)
Annotations:
  kubernetes.io/ingress.class:  nginx
Events:
  Type    Reason  Age   From                      Message
  ----    ------  ----  ----                      -------
  Normal  CREATE  44s   nginx-ingress-controller  Ingress testing/tomcat

[root@k8s-master1 ingree-nginx]# kubectl get ingresses.extensions -n testing 
NAME     HOSTS                 ADDRESS   PORTS   AGE
tomcat   tomcat.wuxingge.com             80      76s

查看ingress-default-backend的详细信息

kubectl exec -n ingress-nginx -ti nginx-ingress-controller-c9b47ff67-7pwqh -- /bin/sh
$
$ cat nginx.conf

hosts解析

[root@k8s-master1 ingree-nginx]# kubectl get pods -o wide -n ingress-nginx 
NAME                                       READY   STATUS    RESTARTS   AGE   IP            NODE        NOMINATED NODE   READINESS GATES
nginx-ingress-controller-c9b47ff67-vq9cc   1/1     Running   0          85m   10.254.88.3  ** 10.0.0.12**   <none>           <none>
[root@k8s-master1 ingree-nginx]# kubectl get service -o wide -n ingress-nginx 
NAME            TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE   SELECTOR
ingress-nginx   NodePort   10.254.150.28   <none>        80:30080/TCP,443:30443/TCP   77m   app.kubernetes.io/name=ingress-nginx,app.kubernetes.io/part-of=ingress-nginx

10.0.0.12 tomcat.wuxingge.com

访问

http://tomcat.wuxingge.com:30080/

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

wordpress ingress

部署MySQL

创建Secret对象

kubectl create secret generic mysql-pass --from-literal=password=Wxg@123.com

kubectl get secrets

pv

[root@k8s-master1 wordpress]# vim mysql_nfs_pv.yaml 
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv1-nfs
  labels:
    app: pv1-nfs
spec:
  capacity:
    storage: 20Gi
  accessModes:
  - ReadWriteMany
  persistentVolumeReclaimPolicy: Recycle
  nfs:
    server: 10.0.0.11
    path: /data/db

pvc

[root@k8s-master1 wordpress]# vim mysql_nfs_pvc.yaml 
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mysql-pv-claim
  labels:
    app: wordpress
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 20Gi

deployment_service

[root@k8s-master1 wordpress]# vim mysql-deployment.yaml 
apiVersion: v1
kind: Service
metadata:
  name: wordpress-mysql
  labels:
    app: wordpress
spec:
  ports:
    - port: 3306
  selector:
    app: wordpress
    tier: mysql
  clusterIP: None
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: wordpress-mysql
  labels:
    app: wordpress
spec:
  replicas: 1
  selector:
    matchLabels:
      app: wordpress
      tier: mysql
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: wordpress
        tier: mysql
    spec:
      containers:
      - name: mysql
        image: mysql:5.7
        env:
        - name: MYSQL_ROOT_PASSWORD
          valueFrom:
            secretKeyRef:
              name: mysql-pass
              key: password
        ports:
        - name: mysql
          containerPort: 3306
        volumeMounts:
        - name: mysql-persistent-storage
          mountPath: /var/lib/mysql
      volumes:
      - name: mysql-persistent-storage
        persistentVolumeClaim:
          claimName: mysql-pv-claim

官方MySQL镜像

/etc/mysql/mysql.conf.d/mysqld.cnf

部署wordpress

pv

vi wordpress_nfs_pv.yaml

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv2-nfs
  labels:
    app: pv2-nfs
spec:
  capacity:
    storage: 20Gi
  accessModes:
  - ReadWriteMany
  persistentVolumeReclaimPolicy: Recycle
  nfs:
    server: 10.0.0.11
    path: /data/web

pvc

vi wordpress_nfs_pvc.yaml

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: wp-pv-claim
  labels:
    app: wordpress
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 20Gi

deployment-service

vi wordpress-deployment.yaml

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: wordpress
  labels:
    app: wordpress
spec:
  replicas: 2
  selector:
    matchLabels:
      app: wordpress
      tier: frontend
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: wordpress
        tier: frontend
    spec:
      containers:
      - name: wordpress
        image: wordpress:4.8-apache
        env:
        - name: WORDPRESS_DB_HOST
          value: wordpress-mysql
        - name: WORDPRESS_DB_PASSWORD
          valueFrom:
            secretKeyRef:
              name: mysql-pass
              key: password
        ports:
        - name: wordpress
          containerPort: 80
        volumeMounts:
        - name: wordpress-persistent-storage
          mountPath: /var/www/html
      volumes:
      - name: wordpress-persistent-storage
        persistentVolumeClaim:
          claimName: wp-pv-claim
---
apiVersion: v1
kind: Service
metadata:
  name: wordpress
  labels:
    app: wordpress
spec:
  ports:
    - name: wordpress
      port: 80
      targetPort: 80
      protocol: TCP
  selector:
    app: wordpress
    tier: frontend

ingress

vi wordpress-ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: wordpress
  annotations:
    kubernetes.io/ingress.class: "nginx"
spec:
  rules:
  - host: wordpress.wuxingge.com
    http:
      paths:
      - path:
        backend:
          serviceName: wordpress
          servicePort: 80

hosts解析

[root@k8s-master1 ingree-nginx]# kubectl get pods -o wide -n ingress-nginx 
NAME                                       READY   STATUS    RESTARTS   AGE   IP            NODE        NOMINATED NODE   READINESS GATES
nginx-ingress-controller-c9b47ff67-vq9cc   1/1     Running   0          85m   10.254.88.3   **10.0.0.12**   <none>           <none>
[root@k8s-master1 ingree-nginx]# kubectl get service -o wide -n ingress-nginx 
NAME            TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE   SELECTOR
ingress-nginx   NodePort   10.254.150.28   <none>        80:30080/TCP,443:30443/TCP   77m   app.kubernetes.io/name=ingress-nginx,app.kubernetes.io/part-of=ingress-nginx

10.0.0.12 wordpress.wuxingge.com

访问

http://wordpress.wuxingge.com:30080/

ingress-nginx配置https转发dashboard

生成ingress-secret证书

root@k8s-master1 ingree-nginx]# kubectl -n kube-system  create secret tls ingress-secret --key /certs/dashboard.key --cert /certs/dashboard.crt
secret/ingress-secret created

创建ingress服务

vi k8s.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: dashboard-ingress
  namespace: kube-system
  annotations:
    nginx.ingress.kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/secure-backends: "true"
    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
spec:
  tls:
  - hosts:
    - dashboard.wuxingge.com
    secretName: ingress-secret
  rules:
    - host: dashboard.wuxingge.com
      http:
        paths:
        - path: /
          backend:
            serviceName: kubernetes-dashboard
            servicePort: 443

kubectl create -f k8s.yaml       

[root@k8s-master1 yaml]# kubectl get ingresses.extensions -n kube-system 
NAME                HOSTS                    ADDRESS   PORTS     AGE
dashboard-ingress   dashboard.wuxingge.com             80, 443   35s

[root@k8s-master1 yaml]# kubectl describe ingresses.extensions -n kube-system dashboard-ingress 
Name:             dashboard-ingress
Namespace:        kube-system
Address:          
Default backend:  default-http-backend:80 (<none>)
TLS:
  ingress-secret terminates dashboard.wuxingge.com
Rules:
  Host                    Path  Backends
  ----                    ----  --------
  dashboard.wuxingge.com  
                          /   kubernetes-dashboard:443 (10.254.88.4:8443)
Annotations:
  nginx.ingress.kubernetes.io/ssl-passthrough:  true
  nginx.ingress.kubernetes.io/ingress.class:    nginx
  nginx.ingress.kubernetes.io/secure-backends:  true
Events:
  Type    Reason  Age    From                      Message
  ----    ------  ----   ----                      -------
  Normal  CREATE  3m32s  nginx-ingress-controller  Ingress kube-system/dashboard-ingress

hosts解析

[root@k8s-master1 yaml]# kubectl get service -n ingress-nginx 
NAME            TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.254.150.28   <none>        80:30080/TCP,443:**30443**/TCP   14h
[root@k8s-master1 yaml]# kubectl get pods -n ingress-nginx -o wide
NAME                                       READY   STATUS    RESTARTS   AGE   IP            NODE        NOMINATED NODE   READINESS GATES
nginx-ingress-controller-c9b47ff67-vq9cc   1/1     Running   1          14h   10.254.88.3   **10.0.0.12**   <none>           <none>

10.0.0.12 dashboard.wuxingge.com

访问

https://dashboard.wuxingge.com:30443

wuxingge
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
K8S篇之Ingress详解以及用法说明
小橙子的笔记屋
07-08 1767
ingress简介以及用法
《kubernetes-1.8.0》12-addon-ingress-nginx
Hek's blog
11-30 2642
《kubernetes-1.8.0》12-addon-ingress-nginx 《kubernetes 1.8.0 测试环境安装部署》 时间：2017-11-29 一、ingress介绍关于nginx-ingress：官网上摘抄几句： Typically, services and pods have IPs only routable by the cluster networ
Nginx Ingress解析
m0_47495420的博客
06-10 1578
负载均衡负载均衡（Load Balancer，简称 LB）是指把客户端访问的流量通过负载均衡器，然后根据指定的一些负载均衡策略进行转发，最终可以均匀的分摊到后端上游服务器上，然后上游服务器进行响应后再返回数据给客户端。负载均衡的最常见应用是充当反向代理，通过负载均衡，可以大大的提高服务的响应速度、提高并发请求、提高稳定性（防止单点故障）。负载均衡的基本实现方案，从业界来看，一般分为软件和硬件两大类...
Ingress-Nginx
weixin_30413739的博客
07-11 267
注意： 　　本文只用的ingress-nginx版本为0.24.1,可在官方网站自行下载 　　https://github.com/kubernetes/ingress-nginx 一、Ingress-Nginx工作原理 1.ingress controller通过和kubernetes api交互，动态的去感知集群中ingress规则变化， 2.然后读取它，按照自定义...
ingress-nginx
learnalwaystodie的博客
03-26 243
使用Helm3.6 安装 Ingress-nginx - syushin - 博客园1 概述 NGINX Ingress Controller 是使用 Kubernetes Ingress 资源对象构建的，用 ConfigMap 来存储 Nginx 配置的一种 Ingress Conhttps://www.cnblogs.com/syushin/p/15271304.html tag: 改成了v1.5.1 helm install ingress-...
ingress nginx
weixin_46837396的博客
03-17 4355
一、 ingress nginx 1、两个核心概念： # ingress： kubernetes中的一个对象，作用是`定义请求如何转发到service的规则` # ingress controller： `具体实现反向代理及负载均衡的程序`，对ingress定义的规则进行解析，根据配置的规则来实现请求转发，实现方式有很多，比如Nginx, Contour, Haproxy等等 2、Ingress（以Nginx为例）的工作原理如下： 1. 用户编写Ingress规则，`说明哪个域名对应kubernete
ingress-nginx-controller-1.9.yaml
10-18
《Ingress-Nginx控制器与应用部署详解》 在 Kubernetes 集群中，Ingress 是一种用于对外提供服务的资源对象，它定义了外部网络如何访问内部的 Service。Nginx Ingress 控制器是广泛应用的一种解决方案，通过配置 ...
ingress.tar.gz
07-21
标题 "ingress.tar.gz" 涉及的主题是 Kubernetes 网络，特别是关于 Ingress 的概念和使用。Ingress 是 Kubernetes 集群中的一种资源对象，它提供了对外部访问 Kubernetes 服务的方法，通常用于配置 HTTP 和 HTTPS ...
ingress的yaml文件
07-28
在Kubernetes（K8s）集群中，Ingress是一种用于对外提供服务的资源对象，它定义了外部网络如何访问内部的Service。Ingress通常通过配置HTTP/HTTPS路由规则，将入站请求转发到对应的Service。YAML（YAML Ain't Markup...
K8S之ingress-controller-v1.1.2资源清单文件及镜像文件
03-21
原文链接：https://blog.csdn.net/m0_37814112/article/details/123423478
ingress-nginx源码
12-31
ingress-nginx源码分析 ingress在Kubernetes生态系统中扮演着至关重要的角色，它是一个外部网络访问Kubernetes服务的入口控制器。而ingress-nginx是Kubernetes社区中最流行的ingress控制器实现，它基于Nginx web...
nginx-ingress镜像
11-04
nginx-ingress镜像
ingress nginx插件下载
11-12
ingress nginx插件yml文件，免费，免费，免费，免费免费
k8s的ingress-nginx配置
11-30
1.14.0 ingress-nginx配置选项
nginx-ingress详解
最新发布
weixin_43539320的博客
04-15 4002
Kubernetes是一个拥有强大故障恢复功能的集群，当pod挂掉时，集群会重新创建一个pod出来，但是pod的IP也会随之发生变化，为了应对这种情况，引入了service，通过service的标签匹配，来进行后端的pod服务发现，并提供传输层的负载均衡。然后我们再通过service的nodeport模式将端口映射到宿主机，这样我们就完成了集群内的服务对外暴漏。但是如果我们想配置基于http的负载均衡，怎么办呢？
Ingress-高可靠部署架构
qq_38461429的博客
07-11 356
参考链接 • 部署高可靠 Ingress Controller 高可靠部署架构 高可靠Ingress接入层部署说明 • Ingress SLB: Ingress 接入层前端 SLB 实例； • Ingress Node: 部署 Ingress Pod 的集群节点 • Ingress Pod：Ingress 服务实例 这三者之间依据标签node-role.kubernetes.io/ingress=true进行关联： Ingress SLB 后端只会挂载打标node-role.kubernetes.io/
k8s部署ingress-nginx
qq_40208428的博客
10-20 3697
k8s服务对外暴露有三种方式Nodeport: 服务暴露需要在集群每个节点都开放一个同样的端口，通过来访问，如果服务数量多了，开放的端口就难以管理: 大部分情况下只适用于支持外部负载均衡器的云提供商（AWS,阿里云,华为云等）使用。每个服务都会由云服务提供一个IP作为入口，转发相应的流量，但每个LoadBlancer Service都会产生费用，成本比较高。如果想要在内网环境中使用就需要部署网络负载均衡器，比如MetalLB等组件，它主要提供两个功能：地址分配和外部通知。所以这次我们主要来介绍。
k8s——通过暴漏端口实现外部访问服务
树袋熊
11-01 2734
通过nodeport暴漏端口 修改nginx-service.yaml文件 apiVersion: v1 kind: Service metadata: name: nginxdeploy spec: type: NodePort ports: - port: 82 protocol: TCP targetPort: 80 name: http ...
ingress-nginx详解和部署方案
热门推荐
最美dee时光的博客
05-08 5万+
部署ingress-nginx ingress介绍 K8s集群对外暴露服务的方式目前只有三种： Loadblancer；Nodeport；ingress 前两种熟悉起来比较快，而且使用起来也比较方便，在此就不进行介绍了。 下面详细讲解下ingress这个服务，ingress由两部分组成： ingress controller：将新加入的Ingress转化成Nginx的配置文件并使之生效 ingre......
ingress 502
11-25
Ingress 502错误是指在访问Ingress时服务器返回的错误代码。具体表示服务器出现了一些问题，无法提供所请求的页面。 当我们在浏览器访问一个网站时，我们的请求首先会发送到服务器，服务器会进行处理并返回响应给我们的浏览器。在这个过程中，如果服务器在处理我们的请求时遇到了错误，就会返回相应的错误代码。而Ingress 502错误代码则意味着服务器在处理我们的请求时遇到了问题。 Ingress 502错误可能是由于以下几个原因引起的： 1. 服务器过载：服务器处理请求的速度没有跟上请求的速度，导致一些请求无法正常处理，从而返回502错误。 2. 后端服务器故障：服务器上的后端应用程序或数据库等出现了故障，导致服务器无法处理请求。 3. 代理服务器问题：在使用代理服务器时，代理服务器本身出现了问题，无法正常将请求转发到目标服务器。 对于用户而言，遇到Ingress 502错误时，我们建议可以尝试以下几个解决方法： 1. 刷新页面：有时候502错误是暂时的，刷新页面可能会解决问题。 2. 等待一段时间：如果是服务器过载导致的错误，可以等待一段时间后再次尝试访问。 3. 检查网络连接：检查自己的网络连接是否正常，尝试连接其他网站，以确定是否是自己的网络问题。 4. 与网站管理员联系：如果以上方法都无效，可以尝试联系网站管理员报告问题，让其能够及时处理服务器问题。 总的来说，Ingress 502错误代码表示服务器无法正常处理请求，可能是由于服务器过载或故障等原因引起的。需要用户尝试刷新页面、等待一段时间、检查网络连接或与网站管理员联系来解决问题。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

wuxingge

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值