Stefan Prodan

Both `flux_install` and `flux_sync` will be removed in the next release Flux v2.3 in Q2.

Let's remove `.status.latestImage` from status, and display the url and tag in separate columns, I agree with not showing the digest.

`originAnnotations` does not work with Flux, we offer source tracking via `flux trace`.

I suspect tf-controller does a status update using v1alpha1 which reverts the version in etcd, then the API returns that error. Flux applies v1alpha2 according to its inventory record. I...

Well the command @somtochiama posted overrides the resources, that’s not what Flux does. We use server-side apply dry-run.

The command is `kubectl apply --server-side --field-manager=kustomize-controller --dry-run=server` without the field manager it will fail, without —server-side it overrides. cc @somtochiama

Anyway you may want to report this in the tf-controlller repo, IMO there is nothing to do in Flux, we don’t change the API version at sequential applies, if that...

Canceling ongoing upgrades will be covered here: https://github.com/fluxcd/flux2/issues/5584

> failed to wait for object to sync in-cache after patching context deadline exceeded This means the controller stopped receiving data from Kubernetes API, I suspect your Kubernetes controler plane...

> Probably the Liveness probe should still work even if there are problems contacting the control plane Not if you build your controller with Kubernetes controller-runtime. Having the controller running...