为了便于将集群中的服务暴露到集群外部，需要使用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证书

Helm 安装Nginx Ingress的更多相关文章

  1. [经验交流] Kubernetes Nginx Ingress 安装与使用

    Ingress 介绍 Kubernetes 上部署的微服务运行在它的私有网络中, 通过Pod实例的hostPort或Service实例的NodePort可以暴露到主机端口上,便于用户访问.但这样的方法 ...

  2. 国内不fq安装K8S三: 使用helm安装kubernet-dashboard

    目录 3 使用helm安装kubernet-dashboard 3.1 Helm的安装 3.2 使用Helm部署Nginx Ingress 3.3 使用Helm部署dashboard 3.4 使用He ...

  3. Helm 安装部署Kubernetes的dashboard

    Kubernetes Dashboard 是 k8s集群的一个 WEB UI管理工具,代码托管在 github 上,地址:https://github.com/kubernetes/dashboard ...

  4. Nginx Ingress on TKE 部署最佳实践

    概述 开源的 Ingress Controller 的实现使用量最大的莫过于 Nginx Ingress 了,功能强大且性能极高.Nginx Ingress 有多种部署方式,本文将介绍 Nginx I ...

  5. Kubernetes用Helm安装Ingress并踩一下使用的坑

    1 前言 欢迎访问南瓜慢说 www.pkslow.com获取更多精彩文章! Ingress是Kubernetes一个非常重要的Controller,它类似一个路由转发的组件,可以让外界访问Kubern ...

  6. 使用helm安装ingress，实现用域名的方式访问k8s内部应用

    k8s集群版本 k8s集群版本是1.22 提前部署好nginx服务和创建好svc deployment方式部署的nginx服务,1个副本 创建的服务 通过服务可以代理到nginx服务 curl 10. ...

  7. helm 安装prometheus operator 并监控ingress

    1.helm安装 curl https://raw.githubusercontent.com/helm/helm/master/scripts/get > get_helm.shchmod 7 ...

  8. kubernetes 1.14安装部署ingress

    简单介绍: Ingress是Kubernetes API的标准资源类型之一,它其实就是一组基于DNS名称或URL路径把请求转发至指定的Service资源的规则,用来将集群外部的请求流量转发至集群内部. ...

  9. 使用helm安装jenkin和gitlab

    一.使用服务介绍 存储: 阿里云NAS k8s网络插件: calico k8s版本: 1.15.2 二.helm安装 https://www.cnblogs.com/zhangb8042/p/1020 ...

随机推荐

  1. C# 杀掉系统中的进程

    杀掉系统进程之前首先要知道进程名称(说了句废话),这里要注意在任务管理器中的进程名称不一定是真实的名称.打个比方,我们开启一个"记事本",任务管理器中进程名称为"记事本& ...

  2. 全国自考C++程序设计

    一.单项选择题(本大题共20小题,每小题1分,共20分)在每小题列出的四个备选项中 只有一个是符合题目要求的,请将其代码填写在题后的括号内.错选.多选或未选均无 分. 1. 编写C++程序一般需经过的 ...

  3. ES6中的关键字 - let

    let关键字 1.let关键字声明的变量仅仅在自己的块级作用域内起作用,出了块级作用域就不起作用了: var arr2 = []; for (let index = 0; index < 10; ...

  4. python 计算列表内容出现次数

    """python 计算列表内容出现次数""" #方法一: l = ['a','a','b','c','d','b','b','b'] te ...

  5. idea 全局内容搜索和替换

    在做项目时,有时会在整个项目里或指定文件夹下进行全局搜索和替换,这是一个很方便功能.使用方法如下: 一.全局搜索1.使用快捷键Ctrl+Shift+F打开搜索窗口,或者通过点击Edit–>Fin ...

  6. tornado利用装饰器记录每个http请求

    python利用装饰器记录每个http请求 设置装饰器 from functools import wraps from datetime import datetime ""&q ...

  7. contenteditable联合v-html实现数据双向绑定的vue组件

    全手打原创,转载请标明出处:https://www.cnblogs.com/dreamsqin/p/11466197.html 先看最终实现的demo效果图: (1)上面看似文本域的大框是通过给div ...

  8. Dapper安装与使用

    1.VS2015直接使用nuget包搜索Dapper,安装时报错:显示版本不兼容. 于是使用命令安装dapper低版本.  步骤:  打开项目,vs工具---Nuget包管理器--程序包管理器控制台 ...

  9. 总结：WPF中模板需要绑定父级别的ViewModel该如何处理

    原文:总结:WPF中模板需要绑定父级别的ViewModel该如何处理 <ListBox ItemsSource="{Binding ClassCollection}"> ...

  10. SSRS连接ORACLE数据库制作报表

    SSRS报表基于ORACLE数据库做报表示例. 开发环境:VS2010 SQL SERVER 数据库:SQL SERVER 2012 PS:数据库连接部分可能有还有个问题就是ORACLE数据源这一部分 ...