should we create official bitnami images?

[vtuson]

Seems like the project is quite popular and we dont have latest and greatest images that are kept up-to-date.

I would suggest that we create a bitnami official image that does:

• single image that uses a two stage process to build and create the prod/binary image
• base it on mini-deb (at the moment is the easiest way for us to automate the creation of new images)

Would that work for you? @jjo @sebgoa @tylerauerbeck @carrodher

[jjo]

@vtuson +1, looks like a good candidate indeed for bitnami/bitnami-docker-kubewatch
(ie alongside other images we recently added there), also given that src code is pretty
straightforward and well written/documented.

[vtuson]

right, was my thoughts. Happy to add it into the backlog. We need to finish up automating some of the new containers but this should be in the list.

[carrodher]

LGTM, we can include it for future iterations

[sebgoa]

let's hear from @tylerauerbeck see if that would be a problem or not.

[tylerauerbeck]

Completely agree, would love to see this happen. Would just need some help from folks on the bitnami side to make this happen.

[tylerauerbeck]

@jjo @vtuson @carrodher Any update on this?

[carrodher]

Hi @tylerauerbeck, @tompizmor published it a few weeks ago, you can take a look at https://github.com/bitnami/bitnami-docker-kubewatch. AFAIK it is integrated in our pipeline so we are tracking and releasing new versions.

[peterfication]

Here is the respective Helm charts update PR: helm/charts#5871

[tylerauerbeck]

@carrodher Just so that we're all on the same page (and hopefully so we can get this documented on the README), can you explain how exactly this is all rigged up? Specifically, if we make changes in this repo, how do those changes get picked up by the bitnami-docker-kubewatch repo? Then ultimately is the goal to get this integrated with the kubewatch helm chart?

[tompizmor]

Hi @tylerauerbeck!

In Bitnami there is a service continuously checking for new releases of the software that we package. For the kubewatch project, it is tracking the github release page.

When we detect that there is a new release, we have a fully automated pipeline to download the new source code, compile the binary, build a docker image and test it.

If the test passed successfully, we update the Dockerfile in the bitnami-docker-kubewatch repo and create a release of the docker image. This is also automated.

At that point, circle ci automatically build the docker image and push it to Dockerhub and other registries. And finally, it would also send a PR to the kubernetes/chart repo updading the application and chart version and updating the docker image.

Some of the above is already documented in the bitnami-docker-kubewatch readme

[tylerauerbeck]

@tompizmor Thanks for the clarification. This makes a lot more sense now. I'll go ahead and close this issue now that I believe all of this to be rigged up appropriately.