Replies: 2 comments
-
I would open an issue for this instead of a discussion. Also it seems to me this is more an issue with Linkerd and SMI instead of Argo Rollouts (I might be wrong). Be sure to include your linkerd version as well. Also do I understand correctly that you want to use Argo Rollouts for internal services in your cluster? Because for end user services (which is the most common use cases), Traefik is enough. No need for using Linkerd as well. |
Beta Was this translation helpful? Give feedback.
-
As of Linkerd 2.11, they no longer include the SMI CRD in the installation. It must be installed seperately via Helm chart, just follow the instructions here: https://linkerd.io/2.13/tasks/linkerd-smi/ Once we did this, the SMI TrafficSplit was installed and we were able to use Argo Rollouts with Traffic Management via SMI/Linkerd Argo Rollouts will create a TrafficSplit object and the Linkerd adaptor will create a Linkerd ServiceProfile object which will do the actual Linkerd traffic routing |
Beta Was this translation helpful? Give feedback.
-
I'm trying to integrate
rollouts
withlinkerd
andtraefik
using kustomize but when I tried to deploy a rollout it says thatthe server could not find the requested resource (post trafficsplits.split.smi-spec.io)
I saw the issue #2125 and I added the patch to the controller but nothing happenedfull error
Files
argo-rollout.yaml
kustimization.yaml
rollout.yaml
live ClusterRole manifest
Any thoughts to help me solve this?
Beta Was this translation helpful? Give feedback.
All reactions