kubernetes 使用 ingress-nginx转发服务

由于raw.githubusercontent.com国内dns不能解析，我们先临时调整/etc/hosts来解决

tee >> /etc/hosts <<EOF
199.232.28.133    raw.githubusercontent.com
EOF

安装ingress-nginx版本

 curl https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/mandatory.yaml -o nginx-ingress.yaml

If the Image can't be downloaded ,change the image with below

registry.cn-hangzhou.aliyuncs.com/bin_x/nginx-ingress:v0.34.1@sha256:80359bdf124d49264fabf136d2aecadac729b54f16618162194356d3c78ce2fe

执行，一般情况下不会有错误。warning可以忽略

[root@centos7v4-k8s ~]# kubectl apply -f nginx-ingress.yaml
namespace/ingress-nginx created
configmap/nginx-configuration created
configmap/tcp-services created
configmap/udp-services created
serviceaccount/nginx-ingress-serviceaccount created
Warning: rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole
clusterrole.rbac.authorization.k8s.io/nginx-ingress-clusterrole created
Warning: rbac.authorization.k8s.io/v1beta1 Role is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 Role
role.rbac.authorization.k8s.io/nginx-ingress-role created
Warning: rbac.authorization.k8s.io/v1beta1 RoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 RoleBinding
rolebinding.rbac.authorization.k8s.io/nginx-ingress-role-nisa-binding created
Warning: rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
clusterrolebinding.rbac.authorization.k8s.io/nginx-ingress-clusterrole-nisa-binding created
deployment.apps/nginx-ingress-controller created
limitrange/ingress-nginx created[root@centos7v4-k8s ~]# kubectl get pod -n ingress-nginx
NAME                                        READY   STATUS    RESTARTS   AGE
nginx-ingress-controller-54b86f8f7b-j49xg   1/1     Running   1          1m

ingress-nginx的实质也是也个pod，对外提供服务也需要通过nodePort,LB,等，并使用service提供负载均衡。

先创建一个service给ingress-nginx,并执行以下的yaml文件

[root@centos7v4-k8s ~]# cat ingress-service.yaml
apiVersion: v1
kind: Service
metadata:name: ingress-nginxnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
spec:type: NodePortports:- name: httpport: 80targetPort: 80protocol: TCPnodePort: 32080  #http- name: httpsport: 443targetPort: 443protocol: TCPnodePort: 32443  #httpsselector:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx

执行程序看到service已经起来了，访问成功。出现404因为还没有后端服务。默认是404。

[root@centos7v4-k8s ~]# kubectl create -f ingress-service.yaml[root@centos7v4-k8s ~]# kubectl get svc -n ingress-nginx
NAME            TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.10.133.234   <none>        80:32080/TCP,443:32443/TCP   88m[root@centos7v4-k8s ~]# curl 10.10.133.234
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.17.8</center>
</body>
</html>

我们创建一个nginx服务在后端，提供service，并且增加一个ingress的服务

[root@centos7v4-k8s ~]# cat nginx-svc.yaml
apiVersion: v1
kind: Service
metadata:name: nginx-externalnamespace: default
spec:selector:name: nginxports:- port: 80targetPort: 80
---
apiVersion: v1
kind: Pod
metadata:name: nginxlabels:name: nginx
spec:containers:- name: nginximage: nginxports:- containerPort: 80        #源端口
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:name: ingress-nginx-externalnamespace: defaultannotations:kubernetes.io/ingress.class: "nginx"
spec:rules:- host: nginx.yc.com #生产中该域名应当可以被公网解析http:paths:- path:backend:serviceName: nginx-externalservicePort: 80

创建。

[root@centos7v4-k8s ~]# kubectl create -f nginx-svc.yaml[root@centos7v4-k8s ~]# kubectl get svc
NAME             TYPE        CLUSTER-IP      EXTERNAL-IP     PORT(S)    AGE
kubernetes       ClusterIP   10.10.0.1       <none>          443/TCP    46h
mysql            ClusterIP   None            <none>          3306/TCP   45h
mysql-read       ClusterIP   10.10.55.22     <none>          3306/TCP   45h
nginx-external   ClusterIP   10.10.151.190   <none>          80/TCP     14h
nginx-headless   ClusterIP   None            192.168.11.62   80/TCP     43h
[root@centos7v4-k8s ~]# kubectl get pod -o wide
NAME      READY   STATUS    RESTARTS   AGE   IP               NODE            NOMINATED NODE   READINESS GATES
mysql-0   2/2     Running   17         45h   10.122.112.193   centos7v3-k8s   <none>           <none>
mysql-1   2/2     Running   10         45h   10.122.42.193    centos7v2-k8s   <none>           <none>
mysql-2   2/2     Running   7          15h   10.122.103.71    centos7v1-k8s   <none>           <none>
nginx     1/1     Running   0          14h   10.122.42.197    centos7v2-k8s   <none>           <none>
[root@centos7v4-k8s ~]# kubectl get ingress
NAME                     CLASS    HOSTS              ADDRESS         PORTS   AGE
ingress-nginx-external   <none>   nginx.yc.com    10.10.133.234   80      14h

添加dns解析

echo "192.168.11.62 nginx.yc.com" >>/etc/hosts

访问服务


[root@centos7v4-k8s ~]# curl nignx.yc.com:32080
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>body {width: 35em;margin: 0 auto;font-family: Tahoma, Verdana, Arial, sans-serif;}
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p><p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p><p><em>Thank you for using nginx.</em></p>
</body>
</html>

结束

kubernetes 使用 ingress-nginx转发服务相关推荐

Kubernetes Ingress Nginx使用
在此我们不讲述如何部署ingress-controller,只演示如何使用ingress之nginx使用.主要演示如何使用ingress nginx实现我们nginx的多样化配置,从而达到使用ingr ...
k8s 安装ingress nginx controller 并部署.net core ingress服务
192.168.28.132 k8smaster 192.168.28.133 k8snode1 192.168.28.134 k8snode2 192.168.28.135 k8snode3 192 ...
解决通过Nginx转发的服务请求头header中含有下划线的key，其值取不到的问题
解决通过Nginx转发的服务请求头header中含有下划线的key,其值取不到的问题参考文章: (1)解决通过Nginx转发的服务请求头header中含有下划线的key,其值取不到的问题 (2)ht ...
Nginx转发ssh服务
Nginx转发ssh服务一.需求二.nginx配置一.需求当前置机需要转发内网主机的ssh端口号,方便外网直连服务器. 二.nginx配置注:与events, http同级,配置stream ...
nginx根据域名转发服务
背景:申请了一个域名,计划是用这个域名部署三个不同的服务在同一台服务器上,我通过一级.二级域名来区分不同的服务. 如:a.com 对应8080这个服务,b.a.com 对应8081这个服务, c.a ...
k8s 集群 Ingress Nginx传递用户真实IP问题
业务应用经常有需要用到用户真实ip的场景,比如:异地登录的风险预警.访问用户分布统计等功能等.当有这种需求的时候,在业务上容器过程中,如果用到ingress就要注意配置了.通常,用户ip的传递依靠的是 ...
Kubernetes 部署 Ingress 控制器 Traefik v1.7.4
标签: kubernetes ingress traefik nginx haproxy kong 介绍 Traefik Ingress 对象上节课我们学习了在Kubernete ...
kubernetes的ingress：Ingress controller，traefik
文章目录 Ingress介绍 nginx ingress controller ingress URL Rewrite Basic Auth 灰度发布等各种发布方式 HTTPS CertManager ...
架构之美【kubernetes、Prometheus、微服务、LVS负载均衡】
kubernetes kubernetes,简称K8s,是用8代替8个字符"ub ...

kubernetes 使用 ingress-nginx转发服务

kubernetes 使用 ingress-nginx转发服务相关推荐

最新文章

热门文章