Is there an existing issue for this?
What happened?
Following #24502 on #24502 (comment), when deleting the CiliumLoadBalancerIPPool to get around the bug, flux cannot reconcile anymore services, even after applying back the pool.
✗ Kustomization reconciliation failed: Service/network-cluster/nginx-ingress-controller dry-run failed, error: failed to create manager for existing fields: failed to convert new object (network-cluster/nginx-ingress-controller; /v1, Kind=Service) to smd typed: .status.conditions: duplicate entries for key [type="io.cilium/lb-ipam-request-satisfied"]
All services have to be deleted along the pool before being able to reconcile.
Actually I think I saw it once even without deleting the pool
Cilium Version
Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)
Client: 1.13.1 a6be57eb 2023-03-15T19:39:01+01:00 go version go1.19.6 linux/amd64
Daemon: 1.13.1 a6be57eb 2023-03-15T19:39:01+01:00 go version go1.19.6 linux/amd64
Kernel Version
Linux srv1 6.2.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 30 Mar 2023 14:51:14 +0000 x86_64 GNU/Linux
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.3", GitCommit:"9e644106593f3f4aa98f8a84b23db5fa378900bd", GitTreeState:"archive", BuildDate:"2023-03-19T19:47:22Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.4", GitCommit:"f89670c3aa4059d6999cb42e23ccb4f0b9a03979", GitTreeState:"clean", BuildDate:"2023-04-12T12:05:35Z", GoVersion:"go1.19.8", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
cilium-sysdump-20230418-235454.zip
Relevant log output
No response
Anything else?
No response
Code of Conduct
Is there an existing issue for this?
What happened?
Following #24502 on #24502 (comment), when deleting the
CiliumLoadBalancerIPPoolto get around the bug, flux cannot reconcile anymore services, even after applying back the pool.All services have to be deleted along the pool before being able to reconcile.
Actually I think I saw it once even without deleting the pool
Cilium Version
Kernel Version
Kubernetes Version
Sysdump
cilium-sysdump-20230418-235454.zip
Relevant log output
No response
Anything else?
No response
Code of Conduct