Jesse Suen

> The user has an OpenShift cluster without a service mesh installed. Argo Rollouts can still carry out canary deployments on a service level. > I will be making a...

Rollout does not account for other controllers also managing the Ingress which it created, so it currently syncs all annotations from the reference ingress, to the canary ingress. The fix...

@stfnbstl can we work around this issue by explicitly setting rancher annotations under `additionalIngressAnnotations`? ```yaml trafficRouting: nginx: additionalIngressAnnotations: rancher-annotation: xxxxxxxxx ```

> nginx.ingress.kubernetes.io/field.cattle.io/publicEndpoints Ah yes, I forgot `additionalIngressAnnotations` also would also incorporate the prefix. So my workaround will not work. I think we have to go with a fix to preserve...

> The current endpoints don't container the namespace in the URL, so we cannot use GetNamespace to perform namespaced RBAC on them. The current endpoints don't support directories. I'd like...

> This is an incredibly niche case only meant to be used by CI/CD tooling. I doubt this has any use for users of the Helm CLI. @bacongobbler - Argo...

> But I disagree with the currently proposed UX semantics. That's fair. I agree that a chart author maintaining a full list of API versions for K8s versions and passing...

The API server is supposed to generate this. During new installations, we will sometimes see application-controller crash because it started before the api-server had a chance to generate it. Which...

With the unified workflow list API for both live + archived workflows we have to do the following: 1. we need all workflows in the cluster because kubernetes API server...

Kargo does not replace image-updater and it was not an intention to kill this project. I consider image-updater a unix-like spot-solution. On the other hand, Kargo's scope is much larger,...