Stephan Austermühle

Reviewing [the issues of co-existing with Calico](https://metallb.universe.tf/configuration/calico/#ideas-wanted), stumbling upon this, and also seeing #1118 I am wondering if assigning another IP address to a node and binding MetalLB to it...

@murali-reddy, tried this without success. This feature seems to enable some automagic feature that I'm not sure how it works because all nodes are seeing each other over eth0 and...

@janse180: Unfortunately I have not. In Calico you can pass the interface name but I have not found a similar option for kube-router. This makes it impossible to separate workload...

@murali-reddy: See https://docs.projectcalico.org/v3.3/reference/node/configuration#ip-autodetection-methods on how to configure a network interface for inter-Pod network traffic. Basically, it requires setting `IP_AUTODETECTION_METHOD=interface=eth1`. It requires a transfer network configured on the interfaces. Just making...

Any news on this issue?

Just discovered another use-case: I need to mount a `ConfigMap` to a sidecar container that shall be present on all database clusters.

@StephenSorriaux No, I am using the latest available Docker image and added `queries.yaml` to the container image. Meanwhile I am wondering why the metric `replay_lag` from `pg_stat_replication` is [discarded](https://github.com/wrouesnel/postgres_exporter/blob/301976c2180fbd8848193a09df65bb898d0acf50/cmd/postgres_exporter/postgres_exporter.go#L316). Is...

> @stephan2012 do you consider this ready for review? Yes, this PR is ready for review.

Is there any activity on this issue?

In my use-case, I run restic in a Kubernetes cluster and also provide a deployment that offers a kind of restic shell for convenient interactive restores. Here, it would be...