The catalog source pod can not migrate when the node becomes NotReady

[sqwaseda]

What did you do?

1. Apply a CatalogSource resource in a cluster with 3 nodes;
2. A pod is deployed by the CatalogSource;
3. Shut down one of the cluster nodes and make its status to be NotReady;
4. Wait for the catalog source pod becomes Running again.

What did you expect to see?
When one of the cluster node becomes NotReady, the catalog source pod should be migrated to other healthy nodes. And we still can get the PackageManifest and sub this CatalogSource to deploy the operators.

What did you see instead? Under which circumstances?
When the node becomes NotReady, the catalog source pod on this node becomes Terminating. It will not be migrated to other nodes, and the PackageManifest is disappeared.

Possible Solution
Shell we deploy kubernetes workloads (i.e Deploymen) to control the catalog source pod instead of deploying pod by CatalogSource directly. The Deployment will keep the catalog source pod alive and migrate it to other healthy nodes when some of the nodes become NotReady.

[joelanford]

We actually just fixed this in #3201

[sqwaseda]

We actually just fixed this in #3201

That's good! Thanks for your responding and I will close this issue.