Kostis (Codefresh)

I have done some preliminary investigation on this and I am not even sure if it an Argo Rollouts bug or an Istio problem. In particular updating to the latest...

How do you solve this problem right now (before adopting Argo Rollouts)?

I am not sure I understand the use case here @kandeshvari , @odorT You don't want to use a traffic manager and it seems you want to send traffic only...

Should be solved as part of https://github.com/argoproj/argo-rollouts/issues/1323

What would be the recommended solution here? Simply truncating the name would seem to be the quickest workaround, but then we run the danger of having different jobs getting truncated...

There seems to be an upcoming gateway API that can function the same way as SMI but for gateways/ingresses https://github.com/argoproj/argo-rollouts/issues/1438

@asoorm There is now a Kubernetes API Gateway spec https://gateway-api.sigs.k8s.io/ and the respective Argo Rollouts plugin https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/ Maybe Tyk can become one of the implementations? https://gateway-api.sigs.k8s.io/implementations/

Since 1.5 Argo Rollouts now has a plugin system :-) https://argo-rollouts.readthedocs.io/en/stable/features/traffic-management/plugins/

Since version 1.5 Argo Rollouts supports plugins. So anybody can add support for SignalFX outside of the core Argo Rollouts source code https://argo-rollouts.readthedocs.io/en/stable/analysis/plugins/

Hello. It seems to me that you are abusing the metric analysis system as a way to run pre-sync hooks. If you are already using Argo CD, wouldn't it be...