为了便于将集群中的服务暴露到集群外部，需要使用Ingress。接下来使用Helm将Nginx Ingress部署到Kubernetes上。 Nginx Ingress Controller被部署在Kubernetes的边缘节点上。

这里将master作为边缘节点，打上label

[root@master /]# kubectl label node master node-role.kubernetes.io/edge=

node/master labeled

[root@master /]# kubectl get nodes

NAME      STATUS   ROLES         AGE    VERSION

master    Ready    edge,master   4d3h   v1.15.1

slaver1   Ready    <none>        4d2h   v1.15.1

slaver2   Ready    <none>        4d2h   v1.15.1

安装

使用yaml配置文件安装

stable/nginx-ingress chart的值文件ingress-nginx.yaml如下：

controller:

  replicaCount: 1

  hostNetwork: true

  nodeSelector:

    node-role.kubernetes.io/edge: ''

  affinity:

    podAntiAffinity:

        requiredDuringSchedulingIgnoredDuringExecution:

        - labelSelector:

            matchExpressions:

            - key: app

              operator: In

              values:

              - nginx-ingress

            - key: component

              operator: In

              values:

              - controller

          topologyKey: kubernetes.io/hostname

  tolerations:

      - key: node-role.kubernetes.io/master

        operator: Exists

        effect: NoSchedule

      - key: node-role.kubernetes.io/master

        operator: Exists

        effect: PreferNoSchedule

defaultBackend:

  nodeSelector:

    node-role.kubernetes.io/edge: ''

  tolerations:

      - key: node-role.kubernetes.io/master

        operator: Exists

        effect: NoSchedule

      - key: node-role.kubernetes.io/master

        operator: Exists

        effect: PreferNoSchedule

完整版的nginx-ingress

nginx ingress controller的副本数replicaCount为1，将被调度到node1这个边缘节点上。这里并没有指定nginx ingress controller service的externalIPs，而是通过hostNetwork: true设置nginx ingress controller使用宿主机网络。

helm repo update

helm install stable/nginx-ingress \

-n nginx-ingress \

--namespace kube-system  \

-f ingress-nginx.yaml

具体信息：

[root@master /]# helm install stable/nginx-ingress -n nginx-ingress --namespace kube-system -f ingress-nginx.yaml

NAME:   nginx-ingress

LAST DEPLOYED: Tue Jul 30 15:29:31 2019

NAMESPACE: kube-system

STATUS: DEPLOYED

RESOURCES:

==> v1/ConfigMap

NAME                      DATA  AGE

nginx-ingress-controller  1     <invalid>

==> v1/Pod(related)

NAME                                           READY  STATUS             RESTARTS  AGE

nginx-ingress-controller-657658b9b-xxq8r       0/1    ContainerCreating  0         <invalid>

nginx-ingress-default-backend-f8b68765c-fgjfs  0/1    ContainerCreating  0         <invalid>

==> v1/Service

NAME                           TYPE          CLUSTER-IP      EXTERNAL-IP  PORT(S)                     AGE

nginx-ingress-controller       LoadBalancer  10.108.248.196  <pending>    80:30839/TCP,443:32156/TCP  <invalid>

nginx-ingress-default-backend  ClusterIP     10.97.98.91     <none>       80/TCP                      <invalid>

==> v1beta1/Deployment

NAME                           READY  UP-TO-DATE  AVAILABLE  AGE

nginx-ingress-controller       0/1    1           0          <invalid>

nginx-ingress-default-backend  0/1    1           0          <invalid>

==> v1beta1/PodDisruptionBudget

NAME                           MIN AVAILABLE  MAX UNAVAILABLE  ALLOWED DISRUPTIONS  AGE

nginx-ingress-controller       1              N/A              0                    <invalid>

nginx-ingress-default-backend  1              N/A              0                    <invalid>

NOTES:

The nginx-ingress controller has been installed.

It may take a few minutes for the LoadBalancer IP to be available.

You can watch the status by running 'kubectl --namespace kube-system get services -o wide -w nginx-ingress-controller'

An example Ingress that makes use of the controller:

  apiVersion: extensions/v1beta1

  kind: Ingress

  metadata:

    annotations:

      kubernetes.io/ingress.class: nginx

    name: example

    namespace: foo

  spec:

    rules:

      - host: www.example.com

        http:

          paths:

            - backend:

                serviceName: exampleService

                servicePort: 80

              path: /

    # This section is only required if TLS is to be enabled for the Ingress

    tls:

        - hosts:

            - www.example.com

          secretName: example-tls

If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:

  apiVersion: v1

  kind: Secret

  metadata:

    name: example-tls

    namespace: foo

  data:

    tls.crt: <base64 encoded cert>

    tls.key: <base64 encoded key>

  type: kubernetes.io/tls

直接使用命令安装

helm install stable/nginx-ingress \

-n nginx-ingress \

--namespace kube-system  \

--set controller.hostNetwork=true，rbac.create=true \

--set controller.replicaCount=1

输出：

[root@master /]# helm install stable/nginx-ingress \

> -n nginx-ingress \

> --namespace kube-system  \

> --set controller.hostNetwork=true，rbac.create=true \

> --set controller.replicaCount=1

Error: release nginx-ingress failed: Deployment in version "v1beta1" cannot be handled as a Deployment: v1beta1.Deployment.Spec: v1beta1.DeploymentSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.HostNetwork: ReadBool: expect t or f, but found ", error found in #10 byte of ...|Network":"true，rba|..., bigger context ...|s":{}}],"dnsPolicy":"ClusterFirst","hostNetwork":"true，rbac.create=true","serviceAccountName":"def|...

安装异常，我这里的helm安装的时候没有设置rbac，去掉重新安装即可

[root@master /]# helm install stable/nginx-ingress \

> -n nginx-ingress \

> --namespace kube-system \

> --set controller.hostNetwork=true,controller.replicaCount=1

NAME:   nginx-ingress

LAST DEPLOYED: Tue Jul 30 15:19:59 2019

NAMESPACE: kube-system

STATUS: DEPLOYED

RESOURCES:

==> v1/ConfigMap

NAME                      DATA  AGE

nginx-ingress-controller  1     <invalid>

==> v1/Pod(related)

NAME                                           READY  STATUS             RESTARTS  AGE

nginx-ingress-controller-67db56c89f-2hkxq      0/1    ContainerCreating  0         <invalid>

nginx-ingress-default-backend-878d64884-q4fmt  0/1    ContainerCreating  0         <invalid>

==> v1/Service

NAME                           TYPE          CLUSTER-IP      EXTERNAL-IP  PORT(S)                     AGE

nginx-ingress-controller       LoadBalancer  10.108.107.199  <pending>    80:31412/TCP,443:31392/TCP  <invalid>

nginx-ingress-default-backend  ClusterIP     10.107.244.59   <none>       80/TCP                      <invalid>

==> v1beta1/Deployment

NAME                           READY  UP-TO-DATE  AVAILABLE  AGE

nginx-ingress-controller       0/1    1           0          <invalid>

nginx-ingress-default-backend  0/1    1           0          <invalid>

==> v1beta1/PodDisruptionBudget

NAME                           MIN AVAILABLE  MAX UNAVAILABLE  ALLOWED DISRUPTIONS  AGE

nginx-ingress-controller       1              N/A              0                    <invalid>

nginx-ingress-default-backend  1              N/A              0                    <invalid>

NOTES:

The nginx-ingress controller has been installed.

It may take a few minutes for the LoadBalancer IP to be available.

You can watch the status by running 'kubectl --namespace inkube-systemet services -o wide -w nginx-ingress-controller'

An example Ingress that makes use of the controller:

  apiVersion: extensions/v1beta1

  kind: Ingress

  metadata:

    annotations:

      kubernetes.io/ingress.class: nginx

    name: example

    namespace: foo

  spec:

    rules:

      - host: www.example.com

        http:

          paths:

            - backend:

                serviceName: exampleService

                servicePort: 80

              path: /

    # This section is only required if TLS is to be enabled for the Ingress

    tls:

        - hosts:

            - www.example.com

          secretName: example-tls

If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:

  apiVersion: v1

  kind: Secret

  metadata:

    name: example-tls

    namespace: foo

  data:

    tls.crt: <base64 encoded cert>

    tls.key: <base64 encoded key>

  type: kubernetes.io/tls

使用externalIP方式对外暴露服务：

helm install stable/nginx-ingress \

-n nginx-ingress \

--namespace kube-system  \

--set controller.service.externalIPs[0]=18.16.202.163

查看：

[root@master /]# kubectl get po,svc -n kube-system

NAME                                                 READY   STATUS        RESTARTS   AGE

pod/nginx-ingress-controller-7d4f8b4fbc-rv52j        1/1     Running       0          44m

pod/nginx-ingress-default-backend-59944969d4-df8cl   1/1     Running       0          44m

NAME                                    TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)                      AGE

service/nginx-ingress-controller        LoadBalancer   10.103.227.228   18.16.202.163   80:30289/TCP,443:30669/TCP   44m

service/nginx-ingress-default-backend   ClusterIP      10.106.189.109   <none>          80/TCP                       44m

删除nginx-ingress

删除nginx-ingress

[root@master /]# helm delete nginx-ingress

release "nginx-ingress" deleted

[root@master /]# helm ls --all nginx-ingress

NAME         	REVISION	UPDATED                 	STATUS 	CHART              	APP VERSION	NAMESPACE

nginx-ingress	1       	Tue Jul 30 14:31:01 2019	DELETED	nginx-ingress-0.9.5	0.10.2     	kube-system

[root@master /]# helm delete --purge nginx-ingress

release "nginx-ingress" deleted

[root@master /]# helm ls --all nginx-ingress

使用--purge参数可以彻底删除release不留下记录，否则下一次部署的时候不能使用重名的release。

安装成功查看

查看

[root@master /]# kubectl get po,svc -n kube-system -o wide

NAME                                                 READY   STATUS    RESTARTS   AGE   IP              NODE     NOMINATED NODE   READINESS GATES

pod/nginx-ingress-controller-b89575c7f-2xtkk         1/1     Running   0          13m   18.16.202.163   master   <none>           <none>

pod/nginx-ingress-default-backend-7b8b45bd49-g4mbz   1/1     Running   0          13m   10.244.0.23     master   <none>           <none>

NAME                                    TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE   SELECTOR

service/nginx-ingress-controller        LoadBalancer   10.111.25.193    <pending>     80:31577/TCP,443:31246/TCP   13m   app=nginx-ingress,component=controller,release=nginx-ingress

service/nginx-ingress-default-backend   ClusterIP      10.106.126.222   <none>        80/TCP                       13m   app=nginx-ingress,component=default-backend,release=nginx-ingress

helm查看：

[root@master /]# helm ls --all nginx-ingress

NAME         	REVISION	UPDATED                 	STATUS  	CHART              	APP VERSION	NAMESPACE

nginx-ingress	1       	Tue Jul 30 14:39:58 2019	DEPLOYED	nginx-ingress-0.9.5	0.10.2     	kube-system

访问验证：

[root@master /]# curl http://18.16.202.163

default backend - 404

http测试：

[root@master /]# curl -I http://18.16.202.163/healthz/

HTTP/1.1 200 OK

Server: openresty/1.15.8.1

Date: Tue, 20 Aug 2019 10:11:11 GMT

Content-Type: text/html

Content-Length: 0

Connection: keep-alive

https:

[root@master /]# curl -kI  https://k8s.hongda.com/

HTTP/1.1 200 Connection established

HTTP/1.1 200 OK

Server: openresty/1.15.8.1

Date: Tue, 20 Aug 2019 16:22:06 GMT

Content-Type: text/html; charset=utf-8

Content-Length: 990

Connection: keep-alive

Vary: Accept-Encoding

Accept-Ranges: bytes

Cache-Control: no-store

Last-Modified: Mon, 17 Dec 2018 09:04:43 GMT

Strict-Transport-Security: max-age=15724800; includeSubDomains

参考：

使用kubeadm安装Kubernetes 1.15

使用Helm安装Nginx ingress

利用 Helm 快速部署 Ingress

利用cert-manager让Ingress启用免费的HTTPS证书

最新文章

  1. Bubble Cup 8 finals E. Spectator Riots (575E)
  2. 大数据平台架构（flume＋kafka＋hbase＋ELK+storm+redis+mysql）
  3. iOS之清除缓存
  4. Maven的安装配置
  5. XAF点滴：很具体很用实用---处理三个小问题
  6. java语法基本知识2
  7. Android_layout_note
  8. mybatis0208 缓存
  9. Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException
  10. MySQL 5.5 禁用 innodb
  11. OpenWRT 添加应用程序开机启动方法
  12. HDU 1241 DFS
  13. HDU [P1151] Air Raid
  14. Rails报找不到sanitize和raw方法的解决
  15. win10装ubuntu双系统
  16. HDU 4780 Candy Factory(拆点费用流)
  17. table中怎么设置两行间距
  18. Ubuntu 下 vi 输入方向键会变成 ABCD 的解决方法
  19. POJ 2367：Genealogical tree（拓扑排序模板）
  20. C#利用ntsd.exe关闭进程

热门文章

  1. WeakhashMap源码2
  2. hanlp进行命名实体识别
  3. Vim 入门教程
  4. [转帖]Redis持久化--Redis宕机或者出现意外删库导致数据丢失--解决方案
  5. [转帖]k8s 部署问题解决
  6. C语言是什么
  7. java ASM
  8. 简洁的 Python Schema
  9. 使用IDEA创建maven父子工程项目
  10. framework7 下拉刷新、无限滚动