Alexander Block

This will be important for you as well: https://github.com/kluctl/kluctl/pull/416 It moves to using `encoding/json` and json tags instead of yaml tags. It then uses conversion between json/yaml to achieve yaml...

Also, a rebase is required here

fyi, https://github.com/kluctl/kluctl/pull/979 at least fixes validation of such hooks.

Agree that this should be implemented properly. Until then, you can use the Git credentials via [environment variables support](https://kluctl.io/docs/kluctl/reference/commands/environment-variables/#additional-environment-variables) for https+basic auth: KLUCTL_GIT_1_HOST=http://github.com/ KLUCTL_GIT_1_USERNAME=myuser KLUCTL_GIT_1_PASSWORD=mytoken for ssh: KLUCTL_GIT_1_HOST=http://github.com/ KLUCTL_GIT_1_USERNAME=myuser KLUCTL_GIT_1_SSH_KEY=/path/to/private/key...

Important, if you're reviewing this before the release of v2.24.0 of Kluctl, you will need to download the [devel](https://github.com/kluctl/kluctl/releases/tag/devel) release instead of following the installation instructions.

> I think the opposite, you just need to have `docker`, `kind` and run `while ! kustomize build example | kubectl apply -f -; do echo "Retrying to apply resources";...

I've rebased the PR on master and force-pushed. I extracted a few fixes of this PR into the upstream repos: 1. https://github.com/kubeflow/pipelines/pull/10669. I added sortOptions: legacy into the kluctl deployment...

I've rebased on master and force-pushed. For some reason my kluctl based e2e workflows are not being run.

I believe that I found the underlying issue. The replicator is relying on a informer (`cache.NewInformer`) to get informed about updates and then reacts on those by doing the actual...

@martin-helmich As you seem to be one of the devs here, maybe you can look into my analysis?