Dependency on old version of kapp-controller, ytt should be removed

[jorgemoralespou]

When using kapp as library it adds:

• kapp-controller's old version as indirect dependency because of this line https://github.com/carvel-dev/kapp/blob/develop/go.mod#L19
• ytt old version as indirect dependency because of this line https://github.com/carvel-dev/kapp/blob/develop/go.mod#L13

What did you expect: kapp-controller depends on kapp, and so kapp should not depend on kapp-controller. Dependency on ytt and other libs should be upgraded so that they ingest carvel.dev instead

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

[100mik]

We should bump the ytt dependency. It is mainly used for ytt rebase rules.

The deal with kapp however is a bit different, kapp is consumed by kapp-controller as a binary, kapp just has a dependency on kapp-controller because it imports some types (pkgi/app primarily) to have some specific behaviour for these resources. But yep, it should be bumped if out of date 🙏🏼

[Siegfriedk]

I'm currently in the process of maintaining kubeapps and was trying to update golang to 1.25.

Due to the way this dependency work (at least that what i believe) i was unable to get carvel support for kubeapps working and removed ithe carvel plugin for now.

I might try to see how this could be fixed or what the exact issue is, but this will take time. Prefixed would help a lot