While both parts are related, they live on two different levels. The core namespace lives within client (micro-)services, while the lk namespace helps build Kubernetes deployment manifests. The connection between them is the following:

The driver is packaged in an uber-jar, by running lein uberjar in the project directory.

The newly-created uber-jar is copied (manually) to the file rabbit-drivers-uber.jar, located in the root of this repository.

The file rabbit-drivers-uber.jar is tracked in this repository, so when committing it and pushing it upstream it is uploaded to GitHub.

lk/module specifies the URL to this uberjar, so that when it is used in an application, the latest driver version is used.

Note: The URL being used does not refer to a specific version of the uber-jar, but rather to the latest. One needs to be careful when introducing breaking changes.