为 k8s nginx ingress controller添加错误页面

创建错误页面kubectl apply -f error-page.yaml -n ingress-nginxapiVersion: v1kind: ConfigMapmetadata:name: error-pagenamespace: ingress-nginxdata:404.html: |-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Tr

随风奔跑尿飞扬

1504人浏览 · 2020-08-11 11:27:58

随风奔跑尿飞扬 · 2020-08-11 11:27:58 发布

创建错误页面

kubectl apply -f error-page.yaml -n ingress-nginx

apiVersion: v1
kind: ConfigMap
metadata:
  name: error-page
  namespace: ingress-nginx
data:
  404.html: |-
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta charset="UTF-8" http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>404-对不起！您访问的页面不存在</title>
    <style type="text/css">
    .head404{ width:580px; height:234px; margin:50px auto 0 auto; background:url(https://www.daixiaorui.com/Public/images/head404.png) no-repeat; }
    .txtbg404{ width:499px; height:169px; margin:10px auto 0 auto; background:url(https://www.daixiaorui.com/Public/images/txtbg404.png) no-repeat;}
    .txtbg404 .txtbox{ width:390px; position:relative; top:30px; left:60px;color:#eee; font-size:13px;}
    .txtbg404 .txtbox p {margin:5px 0; line-height:18px;}
    .txtbg404 .txtbox .paddingbox { padding-top:15px;}
    .txtbg404 .txtbox p a { color:#eee; text-decoration:none;}
    .txtbg404 .txtbox p a:hover { color:#FC9D1D; text-decoration:underline;}
    </style>
    </head>
    <body bgcolor="#494949">
    <div class="head404"></div>
    </body>
    </html>

可以将yaml中的html代码替换掉。

创建backend

kubectl apply -f backend.yaml -n ingress-nginx

---
apiVersion: v1
kind: Service
metadata:
  name: nginx-errors
  labels:
    app.kubernetes.io/name: nginx-errors
    app.kubernetes.io/part-of: ingress-nginx
spec:
  selector:
    app.kubernetes.io/name: nginx-errors
    app.kubernetes.io/part-of: ingress-nginx
  ports:
  - port: 80
    targetPort: 8080
    name: http
  - port: 443
    targetPort: 8080
    name: https
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-errors
  labels:
    app.kubernetes.io/name: nginx-errors
    app.kubernetes.io/part-of: ingress-nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: nginx-errors
      app.kubernetes.io/part-of: ingress-nginx
  template:
    metadata:
      labels:
        app.kubernetes.io/name: nginx-errors
        app.kubernetes.io/part-of: ingress-nginx
    spec:
      containers:
      - name: nginx-error-server
        image: quay.io/kubernetes-ingress-controller/custom-error-pages-amd64:0.3
        ports:
        - containerPort: 8080
        volumeMounts:
        - name: error-page
          mountPath: /www/404.html
          subPath: 404.html
      volumes:
      - name: error-page
        configMap:
          name: error-page
        # Setting the environment variable DEBUG we can see the headers sent
        #         # by the ingress controller to the backend in the client response.
        #                 # env:
        #                         # - name: DEBUG
        #                                 #   value: "true"

修改ingress nginx配置

kubectl edit cm nginx-configuration -n ingress-nginx
添加 custom-http-errors: 404,503 , 意思是 404和503错误会定向的刚才定义的错误页面。

apiVersion: v1
data:
  custom-http-errors: 404,503
  fastcgi_connect_timeout: 600s
  fastcgi_read_timeout: 600s
  fastcgi_send_timeout: 600s
  proxy-body-size: 2048m
  proxy-protocol: "True"
  proxy_connect_timeout: 600s
  proxy_intercept_errors: "True"
  proxy_read_timeout: 600s
  proxy_send_timeout: 600s
  real-ip-header: X-Forwarded-For
  use-forwarded-headers: "true"
kind: ConfigMap
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"ConfigMap","metadata":{"annotations":{},"labels":{"app.kubernetes.io/name":"ingress-nginx","app.kubernetes.io/part-of":"ingress-nginx"},"name":"nginx-configuration","namespace":"ingress-nginx"}}
  creationTimestamp: "2019-12-23T13:06:06Z"
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
  name: nginx-configuration
  namespace: ingress-nginx
  resourceVersion: "70153039"
  selfLink: /api/v1/namespaces/ingress-nginx/configmaps/nginx-configuration
  uid: 079c4b59-295b-4752-8911-a327e549fc6f

修改ingress ngixn args

编辑ingress部署文件 kubectl edit deploy nginx-ingress-controller -n ingress-nginx
在启动的args添加 --default-backend-service=ingress-nginx/nginx-errors

验证

执行 kubectl get pod -n ingress-nginx 查看pod是否已经重启过，如果没有自动重启，需要杀掉pod。
打开一个不存在的链接，查看是否显示的是定义的错误页面。
部分浏览器不支持页面显示，如谷歌浏览器会显示“无法显示此网站”

K8S/Kubernetes

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

更多推荐

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

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

K8S/Kubernetes

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

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