LanDinh

Yes, that workaround helps. So the thing is that with v1, it used to work with `.coverage` (most likely due to what is mentioned in #456 regarding the bash uploader...

Hi @alex-arica ! I just stumbled upon this as I was adding metrics to all third-party stuff that I use. The way `postgres-exporter` is usually deployed is as a container...

This would make kubegres fit really nicely into other production-ready environments in kubernetes: * kube-prometheus is the easiest way to add monitoring to all of kubernetes, and will automatically spin...

I mean, sure, this would work. But it also means that whenever I want to change something in my configuration (e.g. labels, namespace, ports, whatever), I would have to change...

I think that there's a misunderstanding here. The fact that a resource has some kind of name is part of the Kubernetes API, yes. But the specific name kubegres chooses...

Yes, the name is the identifier in Kubernetes. But the way kubegres (or any operator, for that matter) works is: you offer some kind of "Kubegres API" via the Kubegres...

I just encountered the same thing, and by chance saw that you already opened an issue for it :) In addition to the solution that you proposed, there is a...

I think that there's been a misunderstanding in my alternative suggestion ;) The suggestion is: ``` other pods --> --> service created by kubegres --> named port 5432 --> kubegres...

Here's a minimal example, stripping away about everything not related to ports :) Service: ``` apiVersion: v1 kind: Service metadata: name: some-service-name spec: selector: app: some-label ports: - protocol: TCP...

I think the issue here is that you return user.is_staff, since this is a `BooleanField` and not a simple `bool` - this actually gets saved into the database. So changing...