SideCar dependency caching proxy with object-store backup for container based CI/CD
It can either be used as daemon collocated with the build, or better as a sidecar proxy to a container.
The command line is as simple as can be, without arguments, it will search for a config file (slim.yaml) in the current working directory, if that's not to your liking use the --config flag to point to your config.
This is the original use case, building JVM applications in ephemeral containers, while it is always possible to deploy a nexus or an artifactory in a deploymentset, configuration, security, storage customisation is expensive, and both products are ... well, not lightweight.
-
Create a bucket, and the required service account to access it
-
Inject the service account into a kubernetes secret
-
Inject the config into a kubernetes configmap
-
Prepare your pod specification
-
Run once and appreciates that it works
-
Run twice and love the speed !