Open
Description
Bug Report
The CatalogSource pod blocks kubectl drain
commands as it is not managed by a Kubernetes controller.
What did you do?
Ran kubectl drain <NODE>
on a cluster with a CatalogSource pod present.
What did you expect to see?
The kubectl drain
should have proceeded without the pod causing a failure
What did you see instead? Under which circumstances?
cannot delete Pods not managed by ReplicationController, ReplicaSet, Job, DaemonSet or StatefulSet (use --force to override): ibm-system/addon-catalog-source-f2wnd
This result is due to the pod being not being managed by a Kubernetes controller.
Environment
-
operator-lifecycle-manager version:
0.14.1
-
Kubernetes version information:
1.16
-
Kubernetes cluster kind:
IBM Cloud
Possible Solution
Create a deployment or some other kind of Kubernetes controller to manage the pod rather than just the CatalogSource custom resource.
Additional context