Update to Kargo Render v0.1.0-rc.42

[BenjaminNeale-Heritage]

No description provided.

[hoopty]

@krancour could we consider bumping kargo-render here? It would be nice for the action to get the version that fixes akuity/kargo-render#315

[krancour]

@hoopty Kargo v0.9.0 no longer uses Kargo Render except in some deprecated/legacy components that will be fully removed in its next release. Once Kargo ceases to use Kargo Render, Kargo Render and its Action are likely to be archived.

Adding to this, jumping from rc.40 to rc.42 transitions to a distroless image, which is a big change, and I'd not be shocked if there are undiscovered problems. I am not sure I want to create the possibility of releasing new problems into the world when there's very little chance of us fixing them if we do.

[hoopty]

Ahh, ok - thanks for the insight. As a happy Akuity platform customer we use it for the rendered manifests pattern and we were looking forward to when ArgoCD supports manifests from OCI (instead of git). I'll have to figure out how we best want to render the manifests & generate the OCI (when that is available) and if you have any suggestions would love to hear them.

[krancour]

@hoopty would you consider looking at full blown Kargo? It now supports rendered branches without Kargo Render. imho, Kargo is (or is becoming) to CD what Actions is to CI. Especially if you are already using AKP, I hope you will find Kargo a natural fit.

[BenjaminNeale-Heritage]

@krancour ... We're using Kargo Render (with the GitHub Action) to manage the GitOps config for each cluster. This includes the GitOps config to install Kargo. Kargo will then be used to manage applications running on each cluster.

I haven't tried Kargo v0.9.0 yet but previous versions of Kargo seem to be focused on managing applications and less on managing clusters. It was challenging to bootstrap clusters and manage cluster config within Kargo.

Do you see that the future of Kargo will be to manage GitOps config for both applications (i.e. development teams) and clusters (i.e. platform teams)?

[pvickery-ParamountCommerce]

Once Kargo ceases to use Kargo Render, Kargo Render and its Action are likely to be archived.

@krancour, I want to use Kargo Render to generate the rendered PRs before the main PR is merged so users can view the diffs of the rendered manifests before merging. Then Kargo will merge those PRs for progressive promotion.

Is there any (planned) way to be able to do this without Kargo Render?