Neither kubernetes-master nor openstack-integrator should be responsible for creating or monitoring the openstack-cloud-controller-manager and csi-cinder pods. The plan is to create new standalone k8s charms for those instead, with support for cross-model relations to openstack-integrator or kubernetes-master as needed. The new charms would be responsible for monitoring their own workloads.
I think the correct answer here is to mark this issue as "won't fix" since the pods in question are about to be deprecated. What do you think?
Neither kubernetes-master nor openstack- integrator should be responsible for creating or monitoring the openstack- cloud-controlle r-manager and csi-cinder pods. The plan is to create new standalone k8s charms for those instead, with support for cross-model relations to openstack- integrator or kubernetes-master as needed. The new charms would be responsible for monitoring their own workloads.
I think the correct answer here is to mark this issue as "won't fix" since the pods in question are about to be deprecated. What do you think?