Not writing status to ConfigMap

[chipzoller]

The kube-vip CP in 0.1 will update the kubevip ConfigMap with its status when reconciling a Service of type LoadBalancer. It does this to the .data.kubevip-services key storing its value as JSON. This is going to be problematic for GitOps approaches because unless an exclusion is applied, the CP and the controller are going to fight over reconciliation of the ConfigMap. May just want to think of another approach here like writing to a separate CR which the CP can own.

[lubronzhan]

Does the CP means control plane here?

[chipzoller]

Cloud provider

[lubronzhan]

the CP and the controller are going to fight over reconciliation of the ConfigMap

Thanks, what's the controller here refers to?

[chipzoller]

A GitOps controller like Argo CD or Flux.

[lubronzhan]

Thanks for the explaning.
Looking at the code KubeVipServicesKey is no longer used
It was rewritten here #23
It doesn't show what service is using the vip anymore.
Yeah using configMap is hard to show what ip is in use properly