You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Or to put in another way, th configmap has been copied
$ kubectl get cm -n kube-system kubernetes-services-endpoint
NAME DATA AGE
kubernetes-services-endpoint 2 17d
$ kubectl get cm -n tigera-operator kubernetes-services-endpoint
NAME DATA AGE
kubernetes-services-endpoint 2 8m59s
But the migration gets stuck because the subsequent copies fail.
I managed to move on with the migration after changing from err := c.client.Create to err := c.client.Update, as Update can create resources as well.
Can create a PR for that if interesting, but maybe we want to look into why copyK8sServicesEPConfigMap runs more than once. (Maybe some reason for it?)
The text was updated successfully, but these errors were encountered:
Scratch that, I'm not so certain of that.
Probably just that my update image can do Update because the configmap had already been copied to tigera operator.
Hey guys!
Attempting to migrate from manifest installation from kubespray to the operator following https://docs.tigera.io/calico/latest/operations/operator-migration.
We run calico in ebpf mode.
Ran into the following problem, where the operator tries to copy over the kubernetes-services-endpoint configmap to the tigera-operator namespace:
By the looks of it, the operator runs
operator/pkg/controller/migration/convert/bpf.go
Lines 30 to 46 in fbdd0a6
Only the first one will succeed.
Or to put in another way, th configmap has been copied
But the migration gets stuck because the subsequent copies fail.
I managed to move on with the migration after changing from
err := c.client.Create
toerr := c.client.Update
, as Update can create resources as well.Can create a PR for that if interesting, but maybe we want to look into why
copyK8sServicesEPConfigMap
runs more than once. (Maybe some reason for it?)The text was updated successfully, but these errors were encountered: