gdg VS kaniko

why don't you use a tool like GDG, https://github.com/esnet/gdg to pull all the dashboards and datasources and re-create them. You do need to know the credentials for the DS. I use it with about 200 dashboards without any issue. (Side note, I'm the primary author so #bias)

Version 0.4.0 of GDG https://github.com/esnet/gdg has just been released. It's potential API break from previous version so if you just started using it that's be a great starting point.

- creates docker images. - generates .deb and .rpm packages for all supported architectures - generates a .tar.gz for all my architecture with binaries. - Generates a changelog programmatically and links to GH issues that were addressed. I'll drop these as examples for reference. My CFG: https://github.com/esnet/gdg/blob/master/.goreleaser.yml CICD Cfg: https://github.com/esnet/gdg/blob/master/.github/workflows/release.yml Example Release: https://github.com/esnet/gdg/releases/tag/v0.3.1 In order to do that all I had to do was git tag v0.3.1 git push origin --tags

I'm the primary developer for https://github.com/esnet/gdg so disclaimer / self promotion goes here. I'm always looking for more help / volunteers. If you find it useful or are looking for a feature you'd like to see it's OSS and accepting patches.

I need to organize this a bit better, but as I'm getting a summer intern (hopefully) to help, which means I REALLY need to clean up the project a bit better. https://github.com/esnet/gdg.

I'll drop my own project as well into the mix, cause why not. https://github.com/esnet/gdg.

You have some tools like https://github.com/esnet/gdg

https://github.com/netsage-project/gdg it's a grafana dashboard manager. Called grafana dash-n-grab (gdg) since gdm was taken. :)

If all you need to do is build container, you can use https://github.com/GoogleContainerTools/kaniko

Kaniko for building the container images

kaniko

You should maybe look into Kaniko or use some other build tool

If you are using the docker socket just for building container images, you might want to look into kaniko. It doesn't use docker to build images. If you use the socket also for starting containers (we are actually doing that in our CI pipelines), you could think about limiting the pods Kubernetes schedules on a node (you can change the default of 110 using the kubelet config file).

Check out Kaniko for building containers https://github.com/GoogleContainerTools/kaniko . Only issue is it doesnt support windows containers.

It took less than 5 minutes to install. It quickly analysed the repo and identified easy ways to make the project more secure. Priya Wadhwa, Kaniko

I'd suggest to take a look at the Kaniko project, combined with custom container images in Lambda functions.

kaniko is a tool that allows you to build container images inside Kubernetes without the need for the Docker daemon. Effectively, it allows you to build Docker images without docker build.

Kubernetes prefers to pull containers from registries. You may be able to work around it by specifying a local image in your Kube manifest. Both https://github.com/GoogleContainerTools/kaniko and/ or https://www.devspace.sh/ may help.