一、什么是微服务

用控制器来完成集群的工作负载，那么应用如何暴漏出去？需要通过微服务暴漏出去后才能被访问

Service是一组提供相同服务的Pod对外开放的接口。

借助Service，应用可以实现服务发现和负载均衡。

service默认只支持4层负载均衡能力，没有7层功能。（可以通过Ingress实现）

二微服务的类型

示例：

创建控制器文件并初始化控制器

复制代码

kubectl create deployment timinglee --image myapp:v1  --replicas 2 --dry-run=client -o yaml > timinglee.yaml

生成微服务yaml追加到已有yaml中

复制代码

kubectl expose deployment timinglee --port 80 --target-port 80 --dry-run=client -o yaml >> timinglee.yaml

401 Authorization Required

nginx [root@reg ~]# curl -k https://myapp-tls.timinglee.org -ulee:lee Hello MyApp | Version: v1 | Pod Name 5.3.5 rewrite重定向 #指定默认访问的文件到hostname.html上 [root@k8s-master app]# vim ingress5.yml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: nginx.ingress.kubernetes.io/app-root: /hostname.html nginx.ingress.kubernetes.io/auth-type: basic nginx.ingress.kubernetes.io/auth-secret: auth-web nginx.ingress.kubernetes.io/auth-realm: "Please input username and password" name: ingress5 spec: tls: - hosts: - myapp-tls.timinglee.org secretName: web-tls-secret ingressClassName: nginx rules: - host: myapp-tls.timinglee.org http: paths: - backend: service: name: myapp-v1 port: number: 80 path: / pathType: Prefix [root@k8s-master app]# kubectl apply -f ingress5.yml ingress.networking.k8s.io/ingress5 created [root@k8s-master app]# kubectl describe ingress ingress5 Name: ingress5 Labels: Namespace: default Address: 172.25.254.10 Ingress Class: nginx Default backend: TLS: web-tls-secret terminates myapp-tls.timinglee.org Rules: Host Path Backends ---- ---- -------- myapp-tls.timinglee.org / myapp-v1:80 (10.244.2.31:80) Annotations: nginx.ingress.kubernetes.io/app-root: /hostname.html nginx.ingress.kubernetes.io/auth-realm: Please input username and password nginx.ingress.kubernetes.io/auth-secret: auth-web nginx.ingress.kubernetes.io/auth-type: basic Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Sync 2m16s (x2 over 2m54s) nginx-ingress-controller Scheduled for sync #测试： [root@reg ~]# curl -Lk https://myapp-tls.timinglee.org -ulee:lee myapp-v1-7479d6c54d-j9xc6 [root@reg ~]# curl -Lk https://myapp-tls.timinglee.org/lee/hostname.html -ulee:lee 404 Not Found

404 Not Found

nginx/1.12.2 #解决重定向路径问题 apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: nginx.ingress.kubernetes.io/rewrite-target: /$2 nginx.ingress.kubernetes.io/use-regex: "true" nginx.ingress.kubernetes.io/auth-type: basic nginx.ingress.kubernetes.io/auth-secret: auth-web nginx.ingress.kubernetes.io/auth-realm: "Please input username and password" name: ingress6 spec: tls: - hosts: - myapp-tls.timinglee.org secretName: web-tls-secret ingressClassName: nginx rules: - host: myapp-tls.timinglee.org http: paths: - backend: service: name: myapp-v1 port: number: 80 path: / pathType: Prefix - backend: service: name: myapp-v1 port: number: 80 path: /lee(/|$)(.*) #正则表达式匹配/lee/，/lee/abc pathType: ImplementationSpecific #测试 [root@reg ~]# curl -Lk https://myapp-tls.timinglee.org/lee/hostname.html -ulee:lee myapp-v1-7479d6c54d-j9xc6 ## 六 Canary金丝雀发布 ![](https://i-blog.csdnimg.cn/direct/d17b545b5add40bf930d7690fec963b9.png) 6.1 么是金丝雀发布金丝雀发布（Canary Release）也称为灰度发布，是一种软件发布策略。主要目的是在将新版本的软件全面推广到生产环境之前，先在一小部分用户或服务器上进行测试和验证，以降低因新版本引入重大问题而对整个系统造成的影响。是一种Pod的发布方式。金丝雀发布采取先添加、再删除的方式，保证Pod的总量不低于期望值。并且在更新部分Pod后，暂停更新，当确认新Pod版本运行正常后再进行其他版本的Pod的更新。 6.2 Canary发布方式 header\>cookie \>weiht 其中header和weiht中的最多 6.2.1 基于header（http包头）灰度 ![](https://i-blog.csdnimg.cn/direct/96f5cbeb9a664ce58e19f8b1ef0c37f6.png) 通过Annotaion扩展创建灰度ingress，配置灰度头部key以及value 灰度流量验证完毕后，切换正式ingress到新版本之前我们在做升级时可以通过控制器做滚动更新，默认25%利用header可以使升级更为平滑，通过key 和vule 测试新的业务体系是否有问题。示例： #建立版本1的ingress [root@k8s-master app]# vim ingress7.yml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: name: myapp-v1-ingress spec: ingressClassName: nginx rules: - host: myapp.timinglee.org http: paths: - backend: service: name: myapp-v1 port: number: 80 path: / pathType: Prefix [root@k8s-master app]# kubectl describe ingress myapp-v1-ingress Name: myapp-v1-ingress Labels: Namespace: default Address: 172.25.254.10 Ingress Class: nginx Default backend: Rules: Host Path Backends ---- ---- -------- myapp.timinglee.org / myapp-v1:80 (10.244.2.31:80) Annotations: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Sync 44s (x2 over 73s) nginx-ingress-controller Scheduled for sync #建立基于header的ingress [root@k8s-master app]# vim ingress8.yml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: nginx.ingress.kubernetes.io/canary: "true" nginx.ingress.kubernetes.io/canary-by-header: version nginx.ingress.kubernetes.io/canary-by-header-value: 2 name: myapp-v2-ingress spec: ingressClassName: nginx rules: - host: myapp.timinglee.org http: paths: - backend: service: name: myapp-v2 port: number: 80 path: / pathType: Prefix [root@k8s-master app]# kubectl apply -f ingress8.yml ingress.networking.k8s.io/myapp-v2-ingress created [root@k8s-master app]# kubectl describe ingress myapp-v2-ingress Name: myapp-v2-ingress Labels: Namespace: default Address: Ingress Class: nginx Default backend: Rules: Host Path Backends ---- ---- -------- myapp.timinglee.org / myapp-v2:80 (10.244.2.32:80) Annotations: nginx.ingress.kubernetes.io/canary: true nginx.ingress.kubernetes.io/canary-by-header: version nginx.ingress.kubernetes.io/canary-by-header-value: 2 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Sync 21s nginx-ingress-controller Scheduled for sync #测试： [root@reg ~]# curl myapp.timinglee.org Hello MyApp | Version: v1 | Pod Name [root@reg ~]# curl -H "version: 2" myapp.timinglee.org Hello MyApp | Version: v2 | Pod Name ##### 6.2.2 基于权重的灰度发布 ![](https://i-blog.csdnimg.cn/direct/31aff63583dd4ae99cf6e4a32129c82a.png) * 通过Annotaion拓展 * 创建灰度ingress，配置灰度权重以及总权重 * 灰度流量验证完毕后，切换正式ingress到新版本示例 #基于权重的灰度发布 [root@k8s-master app]# vim ingress8.yml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: nginx.ingress.kubernetes.io/canary: "true" nginx.ingress.kubernetes.io/canary-weight: "10" #更改权重值 nginx.ingress.kubernetes.io/canary-weight-total: "100" name: myapp-v2-ingress spec: ingressClassName: nginx rules: - host: myapp.timinglee.org http: paths: - backend: service: name: myapp-v2 port: number: 80 path: / pathType: Prefix [root@k8s-master app]# kubectl apply -f ingress8.yml ingress.networking.k8s.io/myapp-v2-ingress created #测试： [root@reg ~]# vim check_ingress.sh #!/bin/bash v1=0 v2=0 for (( i=0; i<100; i++)) do response=`curl -s myapp.timinglee.org |grep -c v1` v1=`expr $v1 + $response` v2=`expr $v2 + 1 - $response` done echo "v1:$v1, v2:$v2" [root@reg ~]# sh check_ingress.sh v1:90, v2:10 #更改完毕权重后继续测试可观察变化

k8s中的微服务

一、什么是微服务

二 微服务的类型

401 Authorization Required

404 Not Found

二微服务的类型