The k8s router has a slightly different implementation from the VM router. This means that the current lib that supports the router interface does not work with K8s
Namely the following has a different implementation on the K8s router:
sharing user info to client
k8s router communicates via port
k8s router updates arguments when changing the pebble layer on restart
Solution
To fix this some cases have been made in the charm lib
k8s charm does not provide its admin user/password to the client (instead it will handle this with the mongos_client interface in DPE-5090
Issue
The k8s router has a slightly different implementation from the VM router. This means that the current lib that supports the router interface does not work with K8s
Namely the following has a different implementation on the K8s router:
Solution
To fix this some cases have been made in the charm lib