[英]Canary rollouts with linkerd and argo rollouts
我正在尝试为演示配置金丝雀推出,但我无法让流量拆分与 linkerd 一起使用。 有趣的是,我能够使用 istio 来实现这一点,而且我发现 istio 比 linkerd 复杂得多。
我有一个基本的 go-lang 服务定义,如下所示:
apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
name: fish
spec:
[...]
strategy:
canary:
canaryService: canary-svc
stableService: stable-svc
trafficRouting:
smi: {}
steps:
- setWeight: 5
- pause: {}
- setWeight: 20
- pause: {}
- setWeight: 50
- pause: {}
- setWeight: 80
- pause: {}
---
apiVersion: v1
kind: Service
metadata:
name: canary-svc
spec:
selector:
app: fish
ports:
- name: http
port: 8080
---
apiVersion: v1
kind: Service
metadata:
name: stable-svc
spec:
selector:
app: fish
ports:
- name: http
port: 8080
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: fish
annotations:
kubernetes.io/ingress.class: 'nginx'
cert-manager.io/cluster-issuer: letsencrypt-production
cert-manager.io/acme-challenge-type: dns01
external-dns.alpha.kubernetes.io/hostname: fish.local
nginx.ingress.kubernetes.io/enable-cors: "true"
nginx.ingress.kubernetes.io/cors-allow-methods: "PUT, GET, POST, OPTIONS"
nginx.ingress.kubernetes.io/cors-allow-origin: "*"
nginx.ingress.kubernetes.io/configuration-snippet: |
proxy_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;
spec:
rules:
- host: fish.local
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: stable-svc
port:
number: 8080
当我通过 ArgoCD 进行部署(同步)时,我可以看到流量拆分为 50/50:
- apiVersion: split.smi-spec.io/v1alpha2
kind: TrafficSplit
metadata:
[...]
name: fish
namespace: default
spec:
backends:
- service: canary-svc
weight: "50"
- service: stable-svc
weight: "50"
service: stable-svc
但是,在 while 循环中执行 curl 命令我只能取回 stable-svc。 我唯一一次看到变化是在我将服务完全移动到 100% 之后。
我试图遵循这个: https://argoproj.github.io/argo-rollouts/getting-started/smi/
任何帮助将不胜感激。
谢谢
阅读此内容后: https://linkerd.io/2.10/tasks/using-ingress/我发现您需要使用特殊注释修改您的入口 controller:
$ kubectl get deployment <ingress-controller> -n <ingress-namespace> -o yaml | linkerd inject --ingress - | kubectl apply -f -
TLDR; 如果您想要服务配置文件、流量拆分等 Linkerd 功能,则需要额外的配置才能使 Ingress 控制器的 Linkerd 代理在入口模式下运行。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.