Incorrect PodCIDR in installations.operator.tigera.io ipPools prevented upgrade

[taxilian]

Incorrect PodCIDR in installations.operator.tigera.io ipPools prevented upgrade

[tmjd]

Thank you for the report.

I believe there has been some work started to improve IPPool handling in the operator but I'm not sure if anything has been merged or even made it into a PR yet.

I would have expected the tigerastatus resource named calico to provide a message about the IPPool in the Installation and kubeadm config conflicting instead of needing to dig into the logs or code. tigerastatus is the first line of debugging to be used when there is an issue with the operator.

Yeah the IPPool in the Installation is still used by the operator unfortunately. It is true that the IPPool is only created at startup but the operator when it was initially created did not read in the IPPool resource and we haven't gone back and switched the operator to use the IPPool resources so it still uses the IPPool in the Installation resource.

[taxilian]

Hmm; I do remember looking at the tigerastatus and describing it, but I don't remember what the specific message was.

TBH since I didn't remember that there was an "Installation" resource and none of the documentation for upgrading mentions it at all to remind me I probably wouldn't have realized that Installation was a specific resource type. I really wish you'd called it something like "TigeraInstallConfiguration" or something like that as it would actually make sense without the extra context which is generally not included when referencing a resource.

All that said, I've got things working so I have no dog in the fight anymore -- just wanted to pass along feedback since I know it's often not clear to developers what is or isn't intuitively obvious to users of the system =]