Testing flagger occurs TrafficSplit create error
I'm newbie here. We're testing Blue/Green release with flagger and linkerd on kubernetes, but never make it (have not yet tried other like canary, nor A/B testing).
Described on canary there's a warning below, not sure if this relates, and we tried trafficsplit v1alpha2/v1alpha3/v1alpha4 with no luck.
flagger TrafficSplit rpcdemo-client.linkerd-demo create error: the server could not find the requested resource (post trafficsplits.split.smi-spec.io)
Anyone can help? If need I can provide more info, thanks.
Expected behavior
route traffic to new version.
Additional context
- Flagger version: 1.21.0
- Kubernetes version: 1.22.1
- Service Mesh provider: linkerd 2.11
- Ingress provider: nginx controller 1.0.4
flagger.yaml
apiVersion: flagger.app/v1beta1 kind: Canary metadata: name: rpcdemo-client namespace: linkerd-demo spec: targetRef: apiVersion: apps/v1 kind: Deployment name: rpcdemo-client progressDeadlineSeconds: 60 service: port: 9000 analysis: interval: 10s threshold: 2 iterations: 30 metrics: - name: request-success-rate thresholdRange: min: 99 interval: 1m - name: request-duration thresholdRange: max: 500 interval: 30s
deployment.yaml
apiVersion: apps/v1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: "15" labels: app: rpcdemo-client name: rpcdemo-client namespace: linkerd-demo spec: progressDeadlineSeconds: 600 replicas: 0 revisionHistoryLimit: 10 selector: matchLabels: app: rpcdemo-client strategy: rollingUpdate: maxSurge: 25% maxUnavailable: 25% type: RollingUpdate template: metadata: annotations: linkerd.io/inject: enabled labels: app: rpcdemo-client spec: containers: - args: - $(GRPC_SERVER) - "1000" command: - ./rpcdemo-client env: - name: GRPC_SERVER value: rpcdemo-server.linkerd-demo.svc.cluster.local image: 192.168.100.50:5000/rpcdemo-client imagePullPolicy: IfNotPresent livenessProbe: failureThreshold: 1 httpGet: path: /healthchk port: 9000 scheme: HTTP initialDelaySeconds: 5 periodSeconds: 1 successThreshold: 1 timeoutSeconds: 1 name: rpcdemo-client ports: - containerPort: 9000 name: http protocol: TCP readinessProbe: failureThreshold: 1 httpGet: path: /healthchk port: 9000 scheme: HTTP periodSeconds: 1 successThreshold: 1 timeoutSeconds: 1 resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: File dnsPolicy: ClusterFirst restartPolicy: Always schedulerName: default-scheduler securityContext: {}