Closed zentavr closed 3 months ago
How it's going?
I just stumbled upon this before I started something similar. I really would like to contribute. Can we get this merged so I can add create PRs for e.g. prometheus rule or prometheus scrape config.
@zentavr @vquie sorry for the delay on this, I am drowning in other work.
I merged some changes into main
— e.g. #197 — so now the image is using scratch. So some paths, user id/group id need to be adjust.
I also published a v0.7.0-rc1
just now.
As I mentioned in comments — I think a simple unbound container in the same pod would be helpful. Could be "disabled" on demand, but should be enable by default.
If people have the need for more unbound config or prefer another DNS server, they could disable it and find a more complex chart/manifest to maintain it.
I am generally hesitating to merge this because I don't want the bitnami dependency in my tree. I see that the flexibility is great, but I wonder if this really needed? Can you each add your thoughts?
@vquie — RE: you contributing, you could theoretically add PRs against the fork/branch and we go from there? Maybe @zentavr can add you as a contributor?
Why not to use unbound as a separate container/service?
@zentavr I made an alternative PR #209 addressing what I wanted. No bitnami dependency, by default an unbound in the same pod, and hopefully simpler config.
@vquie please have a look as well.
Adds helm repository for installing the project into Kubernetes