It looks like the gap here is that the ceph-proxy charm doesn't have a relation with the ceph-admin interface, which kubernetes-master is dependent on.
Per https://bugs.launchpad.net/bugs/1840492 back in 2019, the ceph-admin interface was considered experimental and it was recommended that we remove the need for it from kubernetes-master. I would appreciate clarification from the OpenStack team if that is still the case.
It looks like the gap here is that the ceph-proxy charm doesn't have a relation with the ceph-admin interface, which kubernetes-master is dependent on.
Per https:/ /bugs.launchpad .net/bugs/ 1840492 back in 2019, the ceph-admin interface was considered experimental and it was recommended that we remove the need for it from kubernetes-master. I would appreciate clarification from the OpenStack team if that is still the case.