Is kuik GitOps compatible?

[jo-schulz]

Hello everyone, I have a question about the GitOps compatibility of kuik. I / we use a GitOps controller. This continuously monitors the status in Kubernetes (K8s) and compares it with the Git repo. The automatic change of the image reference would create an inconsistency between K8s and Git. In our case, the GitOps Controller would detect a difference to the Git version and remap the image so that the k8s status is the same as in Git. At this point, I must also say that I am not sure whether we would end up in an endless loop of kuik (switching to the local repository) and the GitOps controller (switching to the image as in Git). An option to only push the images to the repo and not to swap them in the cluster would be ideal. In this way, the project can already be implemented to store the images and in a later step it can be evaluated how the process should be implemented with image swapping / remapping.

If you face similar problems, please write in the issue.

If there are already ideas / implementations that would avoid this problem, I would be very grateful for an explanation

[kppullin]

You should be good as long as your objects in git do not create pods directly. Kuik uses a mutating web hook that only patches pods as they're created. It won't mutate the higher level objects such as deployments, statefulsets, daemonsets, or otherwise that you're most likely defining in your git repo.

[whatnick]

We use Flux in a similar way as a GitOps controller. Interested in knowing your experience with Kuik.

[aDisplayName]

We are using rancher fleet for all our deployment. Kuik is deployed with the fleet. All the pod from the fleet managed workloads are all under kuik management, and we have no conflict so far. Just as @kppullin has said, we don't have any Pod directly under gitops management.