Comment 1 for bug 1881740

I'm seeing this with the following scenario:

Deploy CK
Add a k8s model with the original controller
Deploy cs:~containers/coredns-10
Add relation for coredns/kubernetes control plane
juju trust coredns --scope=cluster # required for the new revision of coredns
juju upgrade-charm coredns --switch coredns --channel=1.24/stable

I end up with:
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
k8s-infra foundations-maas k8s_cloud/default 2.9.31 unsupported 17:47:16Z

App Version Status Scale Charm Channel Rev Address Exposed Message
coredns res:coredns-image@695a5e1 active 1 coredns 1.24/stable 18 192.152.183.63 no

Unit Workload Agent Address Ports Message
coredns/0* active idle 59.47.48.31
coredns/3 unknown lost 59.47.81.17 53/UDP,53/TCP,9153/TCP agent lost, see 'juju show-status-log coredns/3'

Offer Application Charm Rev Connected Endpoint Interface Role
coredns coredns coredns 18 1/1 dns-provider kube-dns provider