# Explanation Understand what the service does and how `gopkg-k8s` is exposed: - Learn what `gopkg.in` does for a Go program and why its import paths still matter in [How gopkg.in serves stable import paths](https://canonical.com/juju/docs/gopkg-charm/latest/explanation/gopkg-service/index.html.md). - Follow request routing from the client to the workload in [Ingress](https://canonical.com/juju/docs/gopkg-charm/latest/explanation/ingress/index.html.md). For more details on Juju, charms, and rocks, see the [Juju](https://canonical.com/juju/docs/juju-cli/3.6/reference/juju/), [Charmcraft](https://canonical.com/juju/docs/charmcraft/4/) and [Rockcraft](https://ubuntu.com/containers/rockcraft/docs/latest/) documentation. * [How gopkg.in serves stable import paths](https://canonical.com/juju/docs/gopkg-charm/latest/explanation/gopkg-service/index.html.md) * [Ingress](https://canonical.com/juju/docs/gopkg-charm/latest/explanation/ingress/index.html.md)